[
https://issues.apache.org/jira/browse/CASSANDRA-17568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525312#comment-17525312
]
Stefan Miklosovic commented on CASSANDRA-17568:
-----------------------------------------------
That would be great if you manage to ship it with 4.1 so we have something to
build on. The functionality required for 2) to happen is to basically get all
keyspace / table directories, even of dropped tables. Since it is possible,
your patch in, to list snapshots of dropped tables, I do not think it would be
any problem to get the list of such dropped tables in the first place.
I am not completely sure we manage to get this one in in forseeable future.
Maybe [~rtib] does not know it but we are having feature freeze at 1st May.
> Tool to list data directories
> -----------------------------
>
> Key: CASSANDRA-17568
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17568
> Project: Cassandra
> Issue Type: New Feature
> Components: Tool/nodetool
> Reporter: Tibor Repasi
> Assignee: Tibor Repasi
> Priority: Normal
> Fix For: 4.x
>
>
> When a table is created, dropped and re-created with the same name,
> directories remain within data paths. Operators may be challenged finding out
> which directories belong to existing tables and which may be subject to
> removal. However, the information is available in CQL as well as in MBeans
> via JMX, a convenient access to this information is still missing.
> My proposal is a new nodetool subcommand allowing to list data paths of all
> existing tables.
> {code}
> % bin/nodetool datapaths -- example
> Keyspace : example
> Table : test
> Paths :
>
> /var/lib/cassandra/data/example/test-02f5b8d0c0e311ecb327ff24df5ab301
> ----------------
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
