cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5289) DatabaseDescriptor.hasExistingNoSystemTables return true even with only system keyspace
Date Mon, 04 Mar 2013 13:19:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592183#comment-13592183
] 

Jason Brown commented on CASSANDRA-5289:
----------------------------------------

Honestly, you could debate whether we need that check at all. In either case, all we do after
calling hasExistingNoSystemTables() is tell the user to create some CFs - I think that should
be obvious by now :). I think we can just eliminate that method and the not overwhelmingly
helpful logging, and have startup be nanoseonds more efficient.
                
> 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

Mime
View raw message