Details
-
Improvement
-
Resolution: Fixed
-
Major
-
Cheshire-Cat
-
1
Description
I am not sure what to suggest as the improvement here. But I was quite confused that to create a scope I have to use a rest end point 'collections'. I understand that the feature name is collections and maybe that is why this was chosen.
curl -X POST -v -u Administrator:password \ http://10.143.210.101:8091/pools/default/buckets/testBucket/collections \ -d name=my_scope
If it is not too late, can we change the end point to 'scopes'?
cc Jim Walker
Attachments
Issue Links
- blocks
-
MB-42841 Backup repo: Update collection aware endopints used by the REST client
- Closed
-
MB-42844 couchbase-cli: Update collection aware endpoints used by the REST client
- Closed
-
MB-42817 Incorporate new ns_server endpoints for collections
- Closed
- relates to
-
MB-42841 Backup repo: Update collection aware endopints used by the REST client
- Closed
-
MB-42844 couchbase-cli: Update collection aware endpoints used by the REST client
- Closed
-
CBES-180 Support for Scope and Collection API Changes
- Resolved
-
DOC-7762 REST APIs for creating/deleting scopes and collections are changing
- Resolved
-
KAFKAC-235 Support for Scope and Collection API Changes
- Resolved
-
MB-42817 Incorporate new ns_server endpoints for collections
- Closed
-
MB-42923 REST APIs for creating/deleting scopes and collections are changing
- Closed
-
MB-42924 REST APIs for creating/deleting scopes and collections are changing
- Closed
-
MB-42925 REST APIs for creating/deleting scopes and collections are changing
- Closed
-
MB-42926 REST APIs for creating/deleting scopes and collections are changing
- Closed
-
MB-42927 REST APIs for retrieving/creating/deleting scopes and collections are changing
- Closed
-
MB-42953 QWB: REST APIs for creating/deleting scopes and collections are changing
- Closed
-
MB-42849 Remove legacy collection management REST APIs
- Closed
- links to