cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9306) Test coverage for cqlsh COPY
Date Fri, 22 May 2015 09:27:17 GMT


Stefania commented on CASSANDRA-9306:

Also, I'm guessing the following failures are caused by CqlshCopyTest setup and teardown class

On a branch based on 2.1, I get [this failure|]
which I can reproduce reliably on my box (cassandra-2.1 or cassandra-2.2 plain branches) by
launching {{nosetests -s cqlsh_tests}}:

ERROR: test_eat_glass (cqlsh_tests.TestCqlsh)
Traceback (most recent call last):
  File "/home/stefania/git/cstar/cassandra-dtest/cqlsh_tests/", line 195, in
    'I can eat glass and it does not hurt me' : binascii.a2b_hex("FEEB")
  File "/home/stefania/git/cstar/cassandra-dtest/cqlsh_tests/", line 170, in
    rows = cursor.execute((u"SELECT %s FROM testks.varcharmaptable WHERE varcharkey= '᚛᚛ᚉᚑᚅᚔᚉᚉᚔᚋ ᚔᚈᚔ ᚍᚂᚐᚅᚑ ᚅᚔᚋᚌᚓᚅᚐ᚜';"
% map_name).encode("utf-8"))
  File "build/bdist.linux-x86_64/egg/cassandra/", line 1550, in execute
    result = future.result(timeout)
  File "build/bdist.linux-x86_64/egg/cassandra/", line 3249, in result
    raise self._final_exception
TypeError: unbound method deserialize() must be called with CqlshCopyTest instance as first
argument (got str instance instead)
-------------------- >> begin captured logging << --------------------
dtest: DEBUG: cluster ccm directory: /tmp/dtest-mI4GRt
--------------------- >> end captured logging << ---------------------

The python version is 2.7.6.

> Test coverage for cqlsh COPY
> ----------------------------
>                 Key: CASSANDRA-9306
>                 URL:
>             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 ({{}}) 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

View raw message