[
https://issues.apache.org/jira/browse/CASSANDRA-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858461#comment-16858461
]
Aleksey Yeschenko commented on CASSANDRA-15151:
-----------------------------------------------
The keyspace provided to the client is there only for one purpose - it's the
keyspace that Cassandra will use for queries that don't specify it (that is,
queries that only specify a non-fully qualified table name, for example).
So, yep, this works as intended. Cassandra doesn't currently have proper
multi-tenant support, and, currently, even with auth, all schema is visible to
all users.
> Connection with Cassendra JDBC is accessing all tenant/keyspaces
> ----------------------------------------------------------------
>
> Key: CASSANDRA-15151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15151
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Ravi kiran Rimmanapudi
> Priority: Normal
>
> There are 2 keyspaces eg:
> schema-1 'tenant1'
> schema-1 'tenant2'
> when we get connection to cassandra DB we are passing keyspace paramaeter as
> well but we getting all keyspaces/schemas.
> This behavior is observed on all OS driver (ex: dataStax java driver ) are
> behaving same. i.e even though we pass keyspace param for connection we will
> get all schemas.
> Even commercial DataDirect(progress) java driver is behaving same.
> Is this a known issue at cassandra shared, as it allows to access
> tables/schemas across the tenants.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
