cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11574) COPY FROM command in cqlsh throws error
Date Thu, 21 Apr 2016 08:13:25 GMT


Stefania commented on CASSANDRA-11574:

You're welcome, thanks for helping us debug this.

.pyc and .so are actually Cython extensions and they must be deleted manually or else changing
the .py has not effect. I had no idea they would be present in package deployments. CASSANDRA-11053,
which was delivered in 3.0.5, modified _pylib/setup.py_ so that people can create these files
manually for added performance by typing {{python build_ext --inplace}} in the pylib
folder. They must be generated somewhere when the package is created. [~mshuler]: do you know
how the packaging process uses _pylib/setup.py_?

The initial solution, {{copy_options\['numprocesses'\] = int(opts.pop('numprocesses', self.get_num_processes(16)))}}
is actually correct, provided the .pyc and .so are regenerated by running {{python
build_ext --inplace}} or, as you already pointed out, if they are removed (in which case the
original code also works).

I will prepare a patch so that the Cython extensions also work.

> COPY FROM command in cqlsh throws error
> ---------------------------------------
>                 Key: CASSANDRA-11574
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>         Environment: Operating System: Ubuntu Server 14.04
> JDK: Oracle JDK 8 update 77
> Python: 2.7.6
>            Reporter: Mahafuzur Rahman
>            Assignee: Stefania
>             Fix For: 3.0.6
> Any COPY FROM command in cqlsh is throwing the following error:
> "get_num_processes() takes no keyword arguments"
> Example command: 
> COPY inboxdata (to_user_id,to_user_network,created_time,attachments,from_user_id,from_user_name,from_user_network,id,message,to_user_name,updated_time)
FROM 'inbox.csv';
> Similar commands worked parfectly in the previous versions such as 3.0.4

This message was sent by Atlassian JIRA

View raw message