[
https://issues.apache.org/jira/browse/CASSANDRA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596383#comment-13596383
]
Jonathan Ellis commented on CASSANDRA-5289:
-------------------------------------------
I still see people copying their data files to a new cluster and wondering why
Cassandra reports no table definitions. So I'd prefer to fix the message than
remove it.
Jackson's fix LGTM. Committed, and in 1.2+ fixed the method name typo (should
be Non-.)
> DatabaseDescriptor.hasExistingNoSystemTables return true even with only
> system keyspace
> ---------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5289
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5289
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jackson Chung
> Priority: Minor
> Attachments: 5289.diff
>
>
> The hasExistingNoSystemTables method in DatabaseDescriptor checks for
> directory only.
> On a new start, system KS would be created. This method current return true
> because of it, resulting incorrect/confusing log:
> logger.info("Found table data in data directories. Consider using the CLI to
> define your schema.") ;
--
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
