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

Gaurav commented on CASSANDRA-9207:
-----------------------------------

It is a double column. Below is the schema of table.

CREATE TABLE cron_tasks(
    type varchar,
    starts double,
    chatid varchar,
    status varchar,
    result varchar,
    reason varchar,
    PRIMARY KEY (type, starts,chatid)
);

If precision issue is valid for double as well, then how to resolve it.

> COPY FROM command does not restore all records
> ----------------------------------------------
>
>                 Key: CASSANDRA-9207
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9207
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tools
>         Environment: centOs, cassandra 2.1.1
>            Reporter: Gaurav
>              Labels: COPY, cqlsh
>             Fix For: 2.1.5
>
>         Attachments: cron_task.csv
>
>
> Steps to reproduce:
> 1. run COPY TO command on keyspace A. (on my environment problem occurred on 
> only 1 table out of 19, only thing that io noticed is this table has >1500 
> records and other tables has <1000 records)
> 2. pull the csv file and place it on machine (say machine B)where  other 
> database resides. (In my case this was another instance of amazon machine)
> 3. Now, run the COPY TO command on machine B. (both keyspaces, one on machine 
> A and one on machine B has same schema.)
> Observation:
> 1. when COPY TO command is run for table having records > 1500. Command gave 
> following output:
> Processing 1000 records
> 1573 records copied.
> but when i tried to verify it by running below mentioned commands, i received 
> only 273 records.
> 1. SELECT COUNT(*) FROM table-name;
> 2. SELECT * FROM table-name;
> Note: please let me know if other information needs to be shared with you.
> Also, is there any other way to take the back-up of keyspace and restoring it 
> on other machine.



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

Reply via email to