cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-358) SystemTable.initMetadata throws an NPE when called twice
Date Wed, 12 Aug 2009 18:37:14 GMT

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

Jonathan Ellis commented on CASSANDRA-358:
------------------------------------------

> it doesn't cater for an updateToken call after which it will start returning stale data

the right fix there is to update the cached SMD in updateToken, then.

it seems pretty clear to me that SMD was intended to be a singleton in the original design.

> SystemTable.initMetadata throws an NPE when called twice
> --------------------------------------------------------
>
>                 Key: CASSANDRA-358
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-358
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeff Hodges
>         Attachments: 358-5.patch, 358-7.patch, 358-v8.patch
>
>
> While this is not the expected use case of it, SystemTable.initMetadata throws an NPE
when called twice in the same process.  The error points to tokenColumn being null even through
cf is not at line 111.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message