You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ramzi Rabah (JIRA)" <ji...@apache.org> on 2009/12/09 21:53:18 UTC
[jira] Created: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
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
Affects Versions: 0.5
Reporter: Ramzi Rabah
Fix For: 0.5
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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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-0001-CASSANDRA-618-unittest-that-demonstrates-bug.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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792159#action_12792159 ]
Hudson commented on CASSANDRA-618:
----------------------------------
Integrated in Cassandra #291 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/291/])
> 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.
[jira] Assigned: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans reassigned CASSANDRA-618:
------------------------------------
Assignee: Eric Evans
> 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, v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt, v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-618:
---------------------------------
Attachment: v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.txt
v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.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
> Priority: Minor
> Fix For: 0.5
>
> Attachments: unittest.patch, v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt, v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789576#action_12789576 ]
Eric Evans commented on CASSANDRA-618:
--------------------------------------
The attached patch(s) addresses this by serializing all column names to hex (instead of using the comparators toString()).
> 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, v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt, v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Ramzi Rabah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramzi Rabah updated CASSANDRA-618:
----------------------------------
Attachment: unittest.patch
Attached is a unit test for exporting/importing to json that reproduces this problem
> 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
> Priority: Minor
> Fix For: 0.5
>
> Attachments: unittest.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790319#action_12790319 ]
Eric Evans commented on CASSANDRA-618:
--------------------------------------
Apparently there is something on the order of 1,000 milliseconds in a second. Who knew.
> 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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Ramzi Rabah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789630#action_12789630 ]
Ramzi Rabah commented on CASSANDRA-618:
---------------------------------------
Applying the patch I am getting this error when I run ant clean build test:
[junit] Testcase: testImportSuperCf(org.apache.cassandra.tools.SSTableImportTest): Caused an ERROR
[junit] Invalid localDeleteTime read: -2140491435
[junit] java.io.IOException: Invalid localDeleteTime read: -2140491435
[junit] at org.apache.cassandra.db.SuperColumnSerializer.deserialize(SuperColumn.java:368)
[junit] at org.apache.cassandra.db.SuperColumnSerializer.deserialize(SuperColumn.java:325)
[junit] at org.apache.cassandra.db.filter.SSTableNamesIterator.<init>(SSTableNamesIterator.java:103)
[junit] at org.apache.cassandra.db.filter.NamesQueryFilter.getSSTableColumnIterator(NamesQueryFilter.java:69)
[junit] at org.apache.cassandra.tools.SSTableImportTest.testImportSuperCf(SSTableImportTest.java:63)
> 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, v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt, v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-618:
-------------------------------------
Component/s: Tools
Priority: Minor (was: Major)
Affects Version/s: (was: 0.5)
> 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
> Priority: Minor
> Fix For: 0.5
>
>
> 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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Ramzi Rabah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790353#action_12790353 ]
Ramzi Rabah commented on CASSANDRA-618:
---------------------------------------
in SSTableExport.java for super column name we still use asKey(comparator.getString(column.name()))
change to byteToHex() besides that, looks good
> 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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788317#action_12788317 ]
Jonathan Ellis commented on CASSANDRA-618:
------------------------------------------
Ramzi, could you add a test to SSTableExportTest illustrating the problem?
> 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
> Priority: Minor
> Fix For: 0.5
>
>
> 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.
[jira] Updated: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-618:
---------------------------------
Attachment: v2-0003-do-trivial-arithmetic-correctly.txt
v2-0002-de-serialize-columns-to-from-hex-regardless-of-compara.txt
v2-0001-CASSANDRA-618-unittest-that-demonstrates-bug.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.
[jira] Resolved: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans resolved CASSANDRA-618.
----------------------------------
Resolution: Fixed
Right you are. Man, I'm batting a thousand with this ticket. Thanks Ramzi!
> 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.
[jira] Commented: (CASSANDRA-618) json2sstable/sstable2json don't
export/import correct column names when the column family is of BytesType
ordering
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789746#action_12789746 ]
Jonathan Ellis commented on CASSANDRA-618:
------------------------------------------
I'm getting that error even w/o the patch, even rolling back to code from dec 9 when i know the tests were passing. possibly a change in wall clock time is what is causing the test failure?
> 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, v1-0001-CASSANDRA-618-unittest-that-demonstrates-bug.txt, v1-0002-de-serialize-columns-to-from-hex-regardless-of-compara.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.