Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
Cheshire-Cat
-
Untriaged
-
Unknown
Description
Build : 7.0.0-1622
Setup - 1 node cluster with kv, query and index service
Steps to reproduce :
1. Create a default bucket from UI
2. Create scope - scope1 using N1QL
create scope default:default.scope1
3. Create Collection - collection1 using N1QL
create collection default:default.scope1.collection1
4. Check system:all_keyspaces
select `path` from system:all_keyspaces where `scope` is not missing;
|
[
|
{
|
"path": "default:default.scope1.collection1"
|
},
|
{
|
"path": "default:default._default._default"
|
}
|
]
|
5. Now create another scope using couchbase-cli
/opt/couchbase/bin/couchbase-cli collection-manage --cluster http://localhost:8091 --username Administrator --password password --bucket default --create-scope scope2
|
6. Check system:all_keyspaces. Its still the same as #4.
select `path` from system:all_keyspaces where `scope` is not missing;
|
[
|
{
|
"path": "default:default.scope1.collection1"
|
},
|
{
|
"path": "default:default._default._default"
|
}
|
]
|
7. List scopes on CLI
/opt/couchbase/bin/couchbase-cli collection-manage --cluster http://localhost:8091 --username Administrator --password password --bucket default --list-scopes
|
scope2
|
scope1
|
_default
|
Scope2 is not listed in system:all_keyspaces
Because of this, using N1QL, scope2 cannot be used to create collection.
This issue is also seen with collections created from tools except N1QL. Those collections are not reflected in system:keyspaces.
Attachments
Issue Links
- depends on
-
MB-33236 notification of collections UID changes
-
- Closed
-