cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Supencheck (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7053) USING TIMESTAMP for batches does not work
Date Thu, 17 Apr 2014 22:35:22 GMT

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

Robert Supencheck commented on CASSANDRA-7053:
----------------------------------------------

Replication steps:

1)  Invoke the cqlsh> prompt;
2)  Create a keyspace:
create keyspace test with replication = {'class':'SimpleStrategy','replication_factor':1};
3)  Choose to use the keyspace, "test";
4)  Create a table in the "test" keyspace:
CREATE TABLE test_table ( key text PRIMARY KEY, data text) ;
5)  Attempt a batch insert, using a timestamp, in the table, "test_table":
BEGIN BATCH USING TIMESTAMP 1111111111111111 INSERT INTO test_table (key, data ) VALUES (
'key1', 'some data 1'); INSERT INTO test_table (key, data) VALUES ( 'key2', 'some data 2')
; APPLY BATCH ;
6)  View the timestamps on the newly inserted table entries to observe that the timestamps
are not as specified:
select writetime(data), key, data from test_table;

 writetime(data)  | key  | data
------------------+------+-------------
 1397772023766000 | key1 | some data 1
 1397772023766000 | key2 | some data 2

(2 rows)

*******************
The expected behavior is that the timestamps in the resulting table should be "1111111111111111."


> USING TIMESTAMP for batches does not work
> -----------------------------------------
>
>                 Key: CASSANDRA-7053
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7053
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Supencheck
>              Labels: cqlsh
>
> When using the "USING TIMESTAMP <timestamp>" syntax for a batch statement, the
supplied timestamp is ignored.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message