Having memcached bucket will cause 'select * from system:keyspaces' will fail.

From Centeredge Software:
https://forums.couchbase.com/t/errors-executing-selecting-from-system-keyspaces-with-memcached-bucket-in-cluster/7974

If there is a Memcached bucket in your cluster, the following query always returns errors:

SELECT * FROM system:keyspaces
Example result:

{
"requestID": "53268848-f314-4925-aa01-955ce572c89f",
"signature":

{ "*": "*" }

,
"results": [
{
"keyspaces":

{ "datastore_id": "http://127.0.0.1:8091", "id": "beer-sample", "name": "beer-sample", "namespace_id": "default" }

},
{
"keyspaces":

{ "datastore_id": "http://127.0.0.1:8091", "id": "default", "name": "default", "namespace_id": "default" }

}
],
"errors": [

{ "code": 12013, "msg": "This bucket type is not supported memcached" }

],
"status": "errors",
"metrics":

{ "elapsedTime": "36.9995ms", "executionTime": "36.9995ms", "resultCount": 2, "resultSize": 446, "errorCount": 1 }

}
While the buckets are returned in the "results", the "errors" section and the "status" result indicate a failure. This can be very difficult for a consumer to interpret, as there is no way to differentiate between a fatal error and this error, which is really more of a warning. Since Memcached buckets don't support N1QL or indices, it seems like it would make more sense to just exclude them from the query without error.

This is currently giving us problems with the Simba ODBC driver, which we are using to interface to a business intelligence system. We are unable to do schema imports while there is a Memcached bucket in our cluster.

I have tested this on both 4.0 and 4.5DP.

Thanks,
Brant