Repository navigation
datastore: Set namespace while initing a Dataset #116
Description
According to #85, namespaces are used to differentiate customer data. They could be seen as workspaces of the same data source. From that point, most of our users are likely to need namespaces most of the time.
What we currently do is to provide two different interfaces and key representations for namespace users. Rather than keep doing that, why don't we let them a namespace at the Dataset constructor.
var ds = new Dataset({
projectId: '..',
// ...
namespace: '...'
});Any operation can include a partition ID if a namespace is set.
Activity
rakyll commentedon Aug 19, 2014
Our key representation will be an arbitrary list of <kind, identifier> tuples without namespace magic.
datastore: Namespace should be a dataset-level configuration.
datastore: scope Key creation to include NS. fixes googleapis#116.
datastore: scope Key creation to include NS. fixes googleapis#116.
datastore: scope Key creation to include NS. fixes googleapis#116.
datastore: scope Key creation to include NS. fixes googleapis#116.
Merge pull request #124 from stephenplusplus/namespaces
58 remaining items
chore(package): update nyc to version 12.0.2 (#116)
Merge pull request #116 from GoogleCloudPlatform/style
chore(deps): lock file maintenance (#116)
chore: test on node10 (#116)
chore: test on node10 (#116)
chore(deps): update dependency webpack to v5 (#116)
chore: test on node10 (#116)
build: remove unused clang format (#116)
fix: Pin @types/sinon to last compatible version (#116)
chore: removing node6 CI (#116)
chore: removing node6 CI (#116)
docs(subscription): add mention of auto-leasing (#116)
chore(nodejs_templates): add script logging to node_library populate-…
build: add new kokoro config for coverage and release-please (#116)
build: add new kokoro config for coverage and release-please (#116)