[
https://issues.apache.org/jira/browse/CASSANDRA-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404308#comment-13404308
]
Jonathan Ellis commented on CASSANDRA-4054:
-------------------------------------------
bq. I think we could fix that by splitting the row into {'key': key,
'metadata': {...}, 'columns': [...]}
Thinking about it more ... do we really want a meta[data] object with just a
single sub-object? should we just pull deletion_info out and make it a
top-level field and dispense with the meta container?
Nit: would prefer to spell out "columns" vs "cols"
> SStableImport and SStableExport does not serialize row level deletion
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-4054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4054
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.5
> Reporter: Zhu Han
> Assignee: David Alves
> Priority: Minor
> Fix For: 1.2
>
> Attachments: 4054.patch, 4054.patch
>
>
> SSTableImport and SSTableExport does not serialize/de-serialize the row-level
> deletion info to/from the json file. This brings back the deleted data after
> restore from the json file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
