[
https://issues.apache.org/jira/browse/CASSANDRA-9306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556440#comment-14556440
]
Mikhail Stepura commented on CASSANDRA-9306:
--------------------------------------------
I'm having the same problem using "cassandra-2.0.15" tag
> Test coverage for cqlsh COPY
> ----------------------------
>
> Key: CASSANDRA-9306
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9306
> Project: Cassandra
> Issue Type: Test
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Jim Witschey
> Labels: cqlsh
> Fix For: 2.1.6, 2.0.16, 2.2.0 rc1
>
>
> We need much more thorough test coverage for cqlsh's COPY TO/FROM commands.
> There is one existing basic dtest ({{cqlsh_tests.py:TestCqlsh.test_copy_to}})
> that we can use as a starting point for new tests.
> The following things need to be tested:
> * Non-default delimiters
> * Null fields and non-default null markers
> * Skipping a header line
> * Explicit column ordering
> * Column names that need to be quoted
> * Every supported C* data type
> * Data that fails validation server-side
> * Wrong number of columns
> * Node going down during COPY operation
> In the non-failure cases, the tests should generally inserted data into
> Cassandra, run COPY TO to dump the data to CSV, truncate, run COPY FROM to
> reimport the data, and then verify that the reloaded data matches the
> originally inserted data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
