[
https://issues.apache.org/jira/browse/CASSANDRA-19939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884887#comment-17884887
]
Stefan Miklosovic commented on CASSANDRA-19939:
-----------------------------------------------
[CASSANDRA-19939|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19939]
{noformat}
java17_pre-commit_tests
✓ j17_build 4m 20s
✓ j17_cqlsh_dtests_py311 7m 8s
✓ j17_cqlsh_dtests_py311_vnode 7m 37s
✓ j17_cqlsh_dtests_py38 7m 0s
✓ j17_cqlsh_dtests_py38_vnode 7m 43s
✓ j17_cqlshlib_cython_tests 8m 5s
✓ j17_cqlshlib_tests 7m 10s
✓ j17_dtests 33m 33s
✓ j17_dtests_vnode 35m 44s
✓ j17_unit_tests 15m 31s
✓ j17_utests_oa 15m 24s
✕ j17_dtests_latest 35m 18s
bootstrap_test.TestBootstrap
test_consistent_range_movement_false_with_replica_down_should_succeed
✕ j17_jvm_dtests 23m 34s
org.apache.cassandra.fuzz.ring.ConsistentBootstrapTest
coordinatorIsBehindTest
✕ j17_jvm_dtests_latest_vnode 23m 3s
org.apache.cassandra.distributed.test.tcm.CMSPlacementAfterMoveTest
testMoveToCMS
✕ j17_utests_latest 14m 33s
org.apache.cassandra.db.compaction.CompactionStrategyManagerPendingRepairTest
testFinalizedAndCompactionRace
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4810/workflows/898574ef-2e4e-4618-94fb-2c91fcd231
> 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
