You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/03/18 10:01:33 UTC

[jira] [Commented] (CASSANDRA-11375) COPY FROM fails when importing blob

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

Stefania commented on CASSANDRA-11375:
--------------------------------------

The issue is only reproducible with Python 2.6, Python 2.7 is fine.

Python 2.6 is only supported in cassandra 2.1, so this patch should be committed to 2.1 only:

|[patch|https://github.com/stef1927/cassandra/commits/11375-2.1]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11375-2.1-dtest/]|

[~pauloricardomg] would you mind reviewing?


> COPY FROM fails when importing blob
> -----------------------------------
>
>                 Key: CASSANDRA-11375
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11375
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Philippe Thibaudeau
>            Assignee: Stefania
>             Fix For: 2.1.x
>
>
> When we try to COPY TO a table containing a blob, we get this error 
> COPY test.blobTable FROM '/tmp/test1.csv' WITH NULL='null' AND DELIMITER=',' AND QUOTE='"';
> /opt/apache-cassandra-2.1.13.4/bin/../pylib/cqlshlib/copyutil.py:1602: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
> /opt/apache-cassandra-2.1.13.4/bin/../pylib/cqlshlib/copyutil.py:1850: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
> Failed to import 5 rows: ParseError - fromhex() argument 1 must be unicode, not str -  given up without retries
> Failed to process 5 rows; failed rows written to import_test_blobTable.err
> Same COPY TO function worked fine with 2.1.9
> The csv is generated by doing a COPY FROM on the same table.
> Is there any work around this issue?



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