Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5481218B6D for ; Mon, 23 Nov 2015 05:01:16 +0000 (UTC) Received: (qmail 77489 invoked by uid 500); 23 Nov 2015 05:01:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 77446 invoked by uid 500); 23 Nov 2015 05:01:11 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 77423 invoked by uid 99); 23 Nov 2015 05:01:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Nov 2015 05:01:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EFDDE2C1F5A for ; Mon, 23 Nov 2015 05:01:10 +0000 (UTC) Date: Mon, 23 Nov 2015 05:01:10 +0000 (UTC) From: "ZhaoYang (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-10755) PreparedStatement is the same id for different Japanese katakana characters with same length MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10755?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-10755: --------------------------------- Summary: PreparedStatement is the same id for different Japanese kataka= na 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 characte= rs with same length > -------------------------------------------------------------------------= ------------------- > > Key: CASSANDRA-10755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1075= 5 > Project: Cassandra > Issue Type: Bug > Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04 > Reporter: ZhaoYang > > String q1 =3D "UPDATE table SET value=3D'=E3=82=BF=E3=83=8B=E3=83=A3=E3= =82=A2' WHERE key=3D? AND key2=3D?"; > String q2 =3D "UPDATE table SET value=3D'=E3=83=A3=E3=82=A2=E3=82=BF=E3= =83=8B' WHERE key=3D? AND key2=3D?"; > when using session.prepare(). > q1 and q2 will return the prepared-statement with the same prepared ID, b= ut 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.= =20 > Is it related to how Cassandra cache prepared statement? -- This message was sent by Atlassian JIRA (v6.3.4#6332)