[
https://issues.apache.org/jira/browse/CASSANDRA-17537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17537:
--------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Status: Open (was: Triage Needed)
there are a few things on my plate, so not taking right now; so if someone else
wants to do please go ahead and more than glad to review; once my queue clears
up can start this.
> nodetool compact should support using a key string to find the range to avoid
> operators having to manually do this
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17537
> Project: Cassandra
> Issue Type: New Feature
> Components: Local/Compaction, Tool/nodetool
> Reporter: David Capwell
> Priority: Normal
>
> Its common that a single key needs to be compact, and operators need to do
> the following
> 1) go from key -> token
> 2) generate range
> 3) call nodetool compact with this range
> We can simply this workflow by adding this to compact
> nodetool compact ks.tbl -k “key1"
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
