[jira] [Commented] (CASSANDRA-12909) cqlsh copy cannot parse strings when counters are present

["Stefania (JIRA)" <ji...@apache.org>]

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

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

This fixes it but I still don't understand why we don't already have a UTF-8 encoded string, and why this only happens with non-prepared statements, given that the converters are identical:

|3.0|[patch|https://github.com/apache/cassandra/compare/trunk...stef1927:12909-cqlsh-3.0]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12909-cqlsh-3.0-cqlsh-tests/]|


> 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)