[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10755: - Assignee: Stefan Podkowinski > PreparedStatement is the same id for different Japanese katakana characters > with same length > > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang >Assignee: Stefan Podkowinski > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10755: - Component/s: CQL > PreparedStatement is the same id for different Japanese katakana characters > with same length > > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang >Assignee: Stefan Podkowinski > Labels: client-impacting > Fix For: 2.1.12, 2.2.4, 3.0.1 > > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10755: - Labels: client-impacting (was: ) > PreparedStatement is the same id for different Japanese katakana characters > with same length > > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang >Assignee: Stefan Podkowinski > Labels: client-impacting > Fix For: 2.1.12, 2.2.4, 3.0.1 > > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10755: - Reviewer: Sylvain Lebresne > PreparedStatement is the same id for different Japanese katakana characters > with same length > > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-10755: - Summary: PreparedStatement is the same id for different Japanese katakana characters with same length (was: PreparedStatement is the same id for different Japanese katakana characters but same length) > PreparedStatement is the same id for different Japanese katakana characters > with same length > > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters but same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-10755: - Description: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct. So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1) Please note that the Japanese katakana is the same length in q1 and q2. Is it related to how Cassandra cache prepared statement? was: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID. So if I update using q1 first, all later q2 will not be able to update. Please note that the Japanese katakana is the same length in q1 and q2. Is it related to how Cassandra cache prepared statement? > PreparedStatement is the same id for different Japanese katakana characters > but same length > --- > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters but same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-10755: - Description: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct. So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1) Please note that the Japanese katakana is the same length in q1 and q2. I know it's a bad use case for prepapred-statement for putting value into prepared-query itself. Is it related to how Cassandra cache prepared statement? was: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct. So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1) Please note that the Japanese katakana is the same length in q1 and q2. Is it related to how Cassandra cache prepared statement? > PreparedStatement is the same id for different Japanese katakana characters > but same length > --- > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for prepapred-statement for putting value into > prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters but same length
[ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-10755: - Description: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct. So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1) Please note that the Japanese katakana is the same length in q1 and q2. I know it's a bad use case for putting value into prepared-query itself. Is it related to how Cassandra cache prepared statement? was: String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; when using session.prepare(). q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct. So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1) Please note that the Japanese katakana is the same length in q1 and q2. I know it's a bad use case for prepapred-statement for putting value into prepared-query itself. Is it related to how Cassandra cache prepared statement? > PreparedStatement is the same id for different Japanese katakana characters > but same length > --- > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10755 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 >Reporter: ZhaoYang > > String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?"; > String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, but > the query in prepared-statement is correct. > So if I update using q1 first, all later q2 will not be able to update.( It's > means , it still updates q1) > Please note that the Japanese katakana is the same length in q1 and q2. > I know it's a bad use case for putting value into prepared-query itself. > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
