[
https://issues.apache.org/jira/browse/CASSANDRA-19939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19939:
---------------------------------------
Description:
The utility sstabledump would be more useful if it had an option to display
just tombsones, much like the -e option to display only partition keys.
When tombstones exist, it should display the partition key, clustering columns
and the range, row or cell tombstone.
When investigating tombstone issues, a common way it to run sstabledump.
However, the output can be very large, on the order of gigabytes and scanning
the JSON output for tombstone entries is a hunt-and-peck experience or requires
using a tool like 'jq'. Being able to just view the tombstones would eliminate
the issue of the output being too large and not require extraneous tools.
was:
The utility sstabledump would be more useful if it had an option to display
just tombsones, much like the -e option to display only partition keys.
When tombstones exist, it should display the partition key, clustering columns
and the range, row or cell tombstone.
When investigating tombstones, a common way it to run sstabledump and scan the
potentially very large JSON output for tombstone entries. Being able to just
view the tombstones would eliminate the issue of the output being large.
> Add sstabledump option to display only tombstones
> -------------------------------------------------
>
> Key: CASSANDRA-19939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19939
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Brad Schoening
> Priority: Normal
>
> The utility sstabledump would be more useful if it had an option to display
> just tombsones, much like the -e option to display only partition keys.
> When tombstones exist, it should display the partition key, clustering
> columns and the range, row or cell tombstone.
> When investigating tombstone issues, a common way it to run sstabledump.
> However, the output can be very large, on the order of gigabytes and scanning
> the JSON output for tombstone entries is a hunt-and-peck experience or
> requires using a tool like 'jq'. Being able to just view the tombstones
> would eliminate the issue of the output being too large and not require
> extraneous tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
