[ https://issues.apache.org/jira/browse/CASSANDRA-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Miklosovic updated CASSANDRA-18322: ------------------------------------------ Fix Version/s: 5.0.x (was: 3.0.x) (was: 3.11.x) (was: 4.0.x) (was: 4.1.x) > 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.0.x, 5.x > > Time Spent: 20m > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org