[
https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871331#comment-17871331
]
Stefan Miklosovic edited comment on CASSANDRA-18322 at 8/6/24 1:14 PM:
-----------------------------------------------------------------------
I will give it few days and if nobody steps in I will commit that with the
change above I suggested. We can easily go back but we would need to fix the
dtests as we would lose the ability to realize that keyspace all batch
statements are from. The patch was otherwise already approved.
was (Author: smiklosovic):
I will give it few days and if nobody steps in I will commit that. (as it was
already approved)
> Warn about unqualified prepared statement only if it is a select, update,
> delete, insert
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18322
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Client
> Reporter: Mohammad Aburadeh
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Hi,
> We get the following warnings when we use prepared statements with "create
> keyspace ... " or "drop keyspace" statements.
> "
> {{USE <keyspace>}} with prepared statements is considered to be an
> anti-pattern due to ambiguity in non-qualified table names. Please consider
> removing instances of {{{}Session#setKeyspace(<keyspace>){}}},
> {{Session#execute("USE <keyspace>")}} and {{cluster.newSession(<keyspace>)}}
> from your code, and always use fully qualified table names (e.g.
> <keyspace>.<table>). Keyspace used: null, statement keyspace: null, statement
> id: 8153d922390fdf9a9963bfeda85b2f3b at
> "
> Such statements are already full-qualified. So, why are we getting this
> warning?
> Regards
> Mohammad
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
