[
https://issues.apache.org/jira/browse/CASSANDRA-18920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773998#comment-17773998
]
Brandon Williams commented on CASSANDRA-18920:
----------------------------------------------
I personally don't think we need to be concerned with json vs jsonl. If we are
worried about optimization, then the sstable is more optimized than either
already. json is really more about having a human readable form that is also
machine readable.
> Add jsonl support to sstabledump
> --------------------------------
>
> Key: CASSANDRA-18920
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18920
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Tools
> Reporter: Geoff Lay
> Assignee: Geoff Lay
> Priority: Low
> Fix For: 5.x
>
>
> Add a new option to sstabledump to allow the generation of jsonl format.
> The -l option for sstabledump does not produce valid jsonl.
> [https://jsonlines.org/validator/]
> Valid jsonl removes whitespace, including newlines, to make the format
> compact.
> By adding an option to generate valid jsonl, jsonl can be generated that is
> smaller.
> Smaller output is better for execution time, storage, and transport.
> jsonl also allows the splitting of a file for processing at a known good line
> for processing without parsing the file, as each row is a line.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
