[
https://issues.apache.org/jira/browse/CASSANDRA-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137997#comment-15137997
]
Yuki Morishita commented on CASSANDRA-6719:
-------------------------------------------
[~cngupte] Sorry for not responding this one for awhile.
Are you still interested in working?
Regarding your question,
1. Yes, you should take care of those as well all the way to nodetool.
2. For now, I want to keep current JXM API and behavior as they are, but with
warning message for your new API/behavior.
If you can still work, can you rebase your patch on top of current trunk?
I looked at your current work, and I think you are going in the right direction.
> redesign loadnewsstables
> ------------------------
>
> Key: CASSANDRA-6719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6719
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
> Attachments: 6719.patch
>
>
> CFSMBean.loadNewSSTables scans data directories for new sstables dropped
> there by an external agent. This is dangerous because of possible filename
> conflicts with existing or newly generated sstables.
> Instead, we should support leaving the new sstables in a separate directory
> (specified by a parameter, or configured as a new location in yaml) and take
> care of renaming as necessary automagically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
