cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4251) when loading schema make sure the key and value are not present in the cfIdMap (BiDiMap)
Date Wed, 16 May 2012 12:53:02 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dave Brosius updated CASSANDRA-4251:
------------------------------------

    Attachment: better_schema_load_exs.diff

java.lang.IllegalArgumentException: value already present: 1034
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
        at com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:111)
        at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
        at com.google.common.collect.HashBiMap.put(HashBiMap.java:84)
        at org.apache.cassandra.config.Schema.load(Schema.java:385)
        at org.apache.cassandra.config.Schema.load(Schema.java:106)
        at org.apache.cassandra.config.Schema.load(Schema.java:91)
                
> when loading schema make sure the key and value are not present in the cfIdMap (BiDiMap)
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4251
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4251
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Dave Brosius
>            Priority: Trivial
>         Attachments: better_schema_load_exs.diff
>
>
> google bidimap throws an uncaught runtime exception with less than informative information
when the cfid already exists in the cfIDMap has it as a value. Add a check to the preflight
check of the Schema class instead, so there is better messaging.

--
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

        

Mime
View raw message