[
https://issues.apache.org/jira/browse/CASSANDRA-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404319#comment-13404319
]
David Alves edited comment on CASSANDRA-4054 at 6/29/12 11:36 PM:
------------------------------------------------------------------
the only point I can think of for the metadata container is to ease
maintenance/compatibility down the line (i.e. writing/parsing metadata can
change without having impact on the overall format), then again the less
verbose the output the better (previous format had that in mind and that's why
I used "meta" and "cols" instead of "metadata" and "columns"). I'm happy either
way. wdyt?
was (Author: dr-alves):
the only point I can think of for the metadata container is to ease
maintenance compatibility down the line (i.e. writing/parsing metadata can
change without having impact on the overall format), then again the less
verbose the output the better (previous format had that in mind and that's why
I used "meta" and "cols" instead of "metadata" and "columns"). I'm happy wither
way. wdyt?
> 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
