Details
-
Bug
-
Resolution: Fixed
-
4.5, 4.6
-
*Location*: http://developer.couchbase.com/documentation/server/4.1/n1ql/n1ql-intro/sysinfo.html
*User-Agent*: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
*Referrer*: http://developer.couchbase.com/documentation/server/4.1/n1ql/n1ql-intro/queriesandresults.html
*Screen Resolution*: 1920 x 1080
*Location*: http://developer.couchbase.com/documentation/server/4.1/n1ql/n1ql-intro/sysinfo.html *User-Agent*: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 *Referrer*: http://developer.couchbase.com/documentation/server/4.1/n1ql/n1ql-intro/queriesandresults.html *Screen Resolution*: 1920 x 1080
Description
This page for the first time introduces the concept of keyspaces and states that it's similar to buckets. But it doesn't have details about when exactly a keyspace gets created or how exactly it relates to a bucket.
For example, I just ran the following command on a new installation of couchbase:
SELECT * FROM system:keyspaces;
|
and could see the following results:
{
|
"requestID": "a1a25f6f-3a0e-4e75-8fd0-235ca2429940",
|
"signature": {
|
"*": "*"
|
},
|
"results": [
|
{
|
"keyspaces": {
|
"datastore_id": "http://127.0.0.1:8091",
|
"id": "default",
|
"name": "default",
|
"namespace_id": "default"
|
}
|
},
|
{
|
"keyspaces": {
|
"datastore_id": "http://127.0.0.1:8091",
|
"id": "gamesim-sample",
|
"name": "gamesim-sample",
|
"namespace_id": "default"
|
}
|
},
|
{
|
"keyspaces": {
|
"datastore_id": "http://127.0.0.1:8091",
|
"id": "travel-sample",
|
"name": "travel-sample",
|
"namespace_id": "default"
|
}
|
},
|
{
|
"keyspaces": {
|
"datastore_id": "http://127.0.0.1:8091",
|
"id": "beer-sample",
|
"name": "beer-sample",
|
"namespace_id": "default"
|
}
|
}
|
],
|
"status": "success",
|
"metrics": {
|
"elapsedTime": "171.921577ms",
|
"executionTime": "171.842105ms",
|
"resultCount": 4,
|
"resultSize": 910
|
}
|
}
|
Based on that I can only guess that a keyspace is infact a bucket which I think is incorrect (don't see a reason why it would be called a keyspace if it was indeed a bucket).
In short, the page doesn't explain why a separate `keyspace` term is necessary in N1QL and how it differs from a bucket.
Reporter: Jaikiran
E-mail: jai.forums2013@gmail.com