cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12909) cqlsh copy cannot parse strings when counters are present
Date Wed, 21 Dec 2016 06:48:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766296#comment-15766296
] 

Stefania commented on CASSANDRA-12909:
--------------------------------------

bq. Therefore, in order to avoid converting values to unicode, we can equivalently encode
the query text into utf-8.

I've changed it again so that we encode the column names rather than the query, this covers
one more failure that I found today with a new [test case|https://github.com/riptano/cassandra-dtest/pull/1393/files#diff-2d1d32d5724e8f118d09beb660163899R3124].

Only the 2.2 patch is up-tp-date and CI for 2.2 is pending. I'm waiting for another review
before updating the remaining branches.

> cqlsh copy cannot parse strings when counters are present
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-12909
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12909
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 2.2.x, 3.0.x, 3.x
>
>
> We get parse error {{Failed to import 1 rows: ParseError - argument for 's' must be a
string}} when using the following table and data:
> {code}
> CREATE TABLE ks.test (
>     object_id ascii,
>     user_id timeuuid,
>     counter_id ascii,
>     count counter,
>     PRIMARY KEY ((object_id, user_id), counter_id)
> )
> {code}
> {code}
> EVT:be3bd2d0-a68d-11e6-90d4-1b2a65b8a28a,f7ce3ac0-a66e-11e6-b58e-4e29450fd577,SA,2
> {code}
> The problem is this line [here|https://github.com/apache/cassandra/blob/trunk/pylib/cqlshlib/copyutil.py#L2114],
strings are serialized as unicode rather than ordinary strings but only for non-prepared statements
(unsure why).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message