Rollback datastoreFactory.getDatastoreDefaultNamespace() (GONRG-837)
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Current version of Storage service in Community (deployed from Opengroup GitLab) works with default namespace. But all data, uploaded with storage service from EpamGit (d773a274 version), stored in osdu namespace.
this.datastoreFactory.getDatastore();
`public Datastore getDatastore() {
DatastoreCredential credential = getDatastoreCredential();
return DatastoreOptions.newBuilder()
.setRetrySettings(RETRY_SETTINGS)
.setTransportOptions(TRANSPORT_OPTIONS)
.setCredentials(credential)
.setProjectId(this.tenant.getProjectId())
.setNamespace(this.tenant.getName())
.build().getService();
} `
What is the new/expected behavior?
- Namespace configuration with TenantInfo in DatastoreFactory
Storage service can work with all namespaces in Datastore.
Have you added/updated Unit Tests and Integration Tests?
Any other useful information
Edited by Riabokon Stanislav(EPAM)[GCP]