You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2019/06/07 10:23:00 UTC
[jira] [Updated] (CASSANDRA-15151) Connection with Cassendra JDBC
is accessing all tenant/keyspaces
[ https://issues.apache.org/jira/browse/CASSANDRA-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-15151:
------------------------------------------
Resolution: Not A Bug
Status: Resolved (was: Triage Needed)
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org