cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9306) Test coverage for cqlsh COPY
Date Fri, 15 May 2015 17:25:01 GMT

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

Jim Witschey commented on CASSANDRA-9306:
-----------------------------------------

Filed a [PR for the cqlsh dtests|https://github.com/riptano/cassandra-dtest/pull/278].

> 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: 3.x, 2.1.x
>
>
> 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)

Mime
View raw message