[
https://issues.apache.org/jira/browse/CASSANDRA-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179897#comment-13179897
]
Jonathan Ellis edited comment on CASSANDRA-3697 at 1/4/12 9:27 PM:
-------------------------------------------------------------------
This changes the semantics to throw when there *are* CFs existing.
But that aside, I'm not sure why switching from AssertionError to
RuntimeException improves things?
was (Author: jbellis):
This changes the semantics throw when there *are* CFs existing.
But that aside, I'm not sure why switching from AssertionError to
RuntimeException improves things?
> 'nodetool -h localhost repair' fails when there is an empty ks
> --------------------------------------------------------------
>
> Key: CASSANDRA-3697
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3697
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.6
> Reporter: Joaquin Casares
> Priority: Minor
> Attachments: 3697.diff
>
>
> If there is an empty KS, the assertion error thrown kills the entire repair,
> when a keyspace is not specified.
> To replicate:
> Start a new cluster
> nodetool -h localhost repair
> Create a new keyspace with no column families
> nodetool -h localhost repair
> Assertion error is thrown to the prompt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
