[
https://issues.apache.org/jira/browse/CASSANDRA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461974#comment-13461974
]
Jonathan Ellis commented on CASSANDRA-4464:
-------------------------------------------
Okay, let's take a step back. What things should be applicable to 2i CFs? I
think we can categorize as follows:
Should be included in operations on parent CFs, and allowed for standalone
operation on 2i sstables:
# scrub
# upgradesstables
# invalidate[key|row]cache
# cfstats
Stuff that is not very useful on standalone 2i CFs but harmless:
# flush
# getsstables
# rangekeysample
Stuff that we shouldn't support since foot-shooting potential is so high:
# snapshot
> expose 2I CFs to the rest of nodetool
> -------------------------------------
>
> Key: CASSANDRA-4464
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4464
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.6
>
> Attachments: 4464.txt
>
>
> This was begun in CASSANDRA-4063. We should extend it to scrub as well, and
> probably compact since any sane way to do it for scrub should give the other
> for free.
> Not sure how easy these will be since they go through CompactionManager via
> StorageProxy. I think getValidColumnFamilies could be updated to check for
> index CFs with "dot notation."
> (Other operations like flush or snapshot don't make sense for 2I CFs in
> isolation of their parent.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
