[
https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Evans updated CASSANDRA-618:
---------------------------------
Attachment: (was:
v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.txt)
> json2sstable/sstable2json don't export/import correct column names when the
> column family is of BytesType ordering
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-618
> URL: https://issues.apache.org/jira/browse/CASSANDRA-618
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Ramzi Rabah
> Assignee: Eric Evans
> Priority: Minor
> Fix For: 0.5
>
> Attachments: unittest.patch,
> v2-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt,
> v2-0002-de-serialize-columns-to-from-hex-regardless-of-compara.txt,
> v2-0003-do-trivial-arithmetic-correctly.txt
>
>
> Easy to reproduce.
> 1- start with an empty node.
> 2- run: client.insert("Keyspace1",
> key_user_id,
> new ColumnPath("Standard1", null,
> "name".getBytes("UTF-8")),
> "Ramzi".getBytes("UTF-8"),
> timestamp,
> ConsistencyLevel.ONE)
> 3- flush to get sstable
> 4- sstable2json and export the sstable to a file
> 5- delete sstable
> 6- json2sstable and import the json into a new sstable.
> 7- sstable2json on new sstable, you will see that the name is different than
> the name in the original json file.
> Also do a get on the column and it will return no result.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
