[jira] [Commented] (CASSANDRA-8675) COPY TO/FROM broken for newline characters

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

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

Tyler Hobbs commented on CASSANDRA-8675:
----------------------------------------

It seems like there's actually a separate problem besides the escape char not actually escaping.  At least in the case of the literal newline, {{COPY TO}} is outputting this:

{noformat}
1,"This has a newline\ncharacter"
{noformat}

However, since it's quoted, it should be able to use a literal newline.  If I replace the "\n" with an actual newline in the csv file, I almost get the right thing after COPY FROM:

{noformat}
 id | t
----+---------------------------------
  1 | This has a newline\r\ncharacter
{noformat}

The only difference is there's now a carriage return.  (I think that's solvable through cqlsh options, but I haven't fully investigated yet.)

> COPY TO/FROM broken for newline characters
> ------------------------------------------
>
>                 Key: CASSANDRA-8675
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8675
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: [cqlsh 5.0.1 | Cassandra 2.1.2 | CQL spec 3.2.0 | Native protocol v3]
> Ubuntu 14.04 64-bit
>            Reporter: Lex Lythius
>              Labels: cqlsh
>             Fix For: 2.1.3
>
>         Attachments: copytest.csv
>
>
> Exporting/importing does not preserve contents when texts containing newline (and possibly other) characters are involved:
> {code:sql}
> cqlsh:test> create table if not exists copytest (id int primary key, t text);
> cqlsh:test> insert into copytest (id, t) values (1, 'This has a newline
>         ... character');
> cqlsh:test> insert into copytest (id, t) values (2, 'This has a quote " character');
> cqlsh:test> insert into copytest (id, t) values (3, 'This has a fake tab \t character (typed backslash, t)');
> cqlsh:test> select * from copytest;
>  id | t
> ----+---------------------------------------------------------
>   1 |                           This has a newline\ncharacter
>   2 |                            This has a quote " character
>   3 | This has a fake tab \t character (entered slash-t text)
> (3 rows)
> cqlsh:test> copy copytest to '/tmp/copytest.csv';
> 3 rows exported in 0.034 seconds.
> cqlsh:test> copy copytest from '/tmp/copytest.csv';
> 3 rows imported in 0.005 seconds.
> cqlsh:test> select * from copytest;
>  id | t
> ----+-------------------------------------------------------
>   1 |                          This has a newlinencharacter
>   2 |                          This has a quote " character
>   3 | This has a fake tab \t character (typed backslash, t)
> (3 rows)
> {code}
> I tried replacing \n in the CSV file with \\n, which just expands to \n in the table; and with an actual newline character, which fails with error since it prematurely terminates the record.
> It seems backslashes are only used to take the following character as a literal
> Until this is fixed, what would be the best way to refactor an old table with a new, incompatible structure maintaining its content and name, since we can't rename tables?



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