[
https://issues.apache.org/jira/browse/CASSANDRA-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165171#comment-16165171
]
Aleksey Yeschenko commented on CASSANDRA-13865:
-----------------------------------------------
As it should. The keyspace in the fully qualified keyspace.table name always
take precedence over session's current keyspace in use.
> Non consistent response when setting the keysace in query an explicily
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-13865
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13865
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jaume M
>
> Using the python driver this works and the query is prepared against
> {{my_keyspace}}, {{system}} is ignored.
> {code}
> prepared_statement = self.session.prepare("SELECT * from
> my_keyspace.my_table", keyspace="system")
> {code}
> However this throws a {{InvalidRequest: Error from server: code=2200 [Invalid
> query] message="keyspace madeup_ks does not exist"}}
> {code}
> prepared_statement = self.session.prepare("SELECT * from madeup_ks.my_table",
> keyspace="system")
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
