[
https://issues.apache.org/jira/browse/CASSANDRA-19939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884547#comment-17884547
]
Stefan Miklosovic edited comment on CASSANDRA-19939 at 9/25/24 9:31 AM:
------------------------------------------------------------------------
I think I got it, please pull and try again.
It seems like when I iterate over all rows, I need to "close" that iterator so
it will iterate over it again on actual dumping.
[~bschoeni] btw you can also use -d with -o like "sstabledump -o -d
that-table-Data.db", it will print tombstones in a way more friendly way on one
line, basically, easier to an eye.
was (Author: smiklosovic):
I think I got it, please pull and try again.
It seems like when I iterate over all rows, I need to "close" that iterator so
it will iterate over it again on actual dumping.
[~bschoeni] btw you can also use -d with -o like "sstabledump -o -d
that-table-Data.db", it will print tombstones is way more friendly way on one
line, basically, easier to an eye.
> 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
> Components: Tool/sstable
> Reporter: Brad Schoening
> Assignee: Stefan Miklosovic
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 is 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
