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 Thu, 22 Dec 2016 03:35:58 GMT

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

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

CI looks good. The [failed test|http://cassci.datastax.com/job/stef1927-12909-cqlsh-cqlsh-tests/lastCompletedBuild/cython=yes,label=ctool-lab/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_copy_from_with_wrong_order_or_missing_UDT_fields/]
on trunk is the new test added for CASSANDRA-12959, which is expected to fail since I did
not rebase the patch branch. I verified that it passes locally.

Committed to 2.2 as f4fd0928e6bc56600b7fd4d2469353c8f9d9da7d and merged upwards.

> 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
>          Components: Tools
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 2.2.9, 3.0.11, 3.10
>
>
> 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