You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/07 18:44:51 UTC
[jira] [Resolved] (CASSANDRA-3461) Server-side fatal exception when
mixing column types in DynamicCompositeType
[ https://issues.apache.org/jira/browse/CASSANDRA-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne resolved CASSANDRA-3461.
-----------------------------------------
Resolution: Won't Fix
Resolving as won't fix since there is really nothing we can do about it.
> Server-side fatal exception when mixing column types in DynamicCompositeType
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-3461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3461
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Environment: JDK 1.6.0_26
> Reporter: Carlos Carrasco
> Assignee: Sylvain Lebresne
>
> Running this CLI script with cause the Cassandra server to throw a fatal exception, and the CLI to hang for some seconds and then just display "null":
> create keyspace Test;
> use Test;
> create column family Composite with comparator ='DynamicCompositeType (a=>AsciiType,s=>UTF8Type)';
> set Composite[ascii('key')]['s@one']=ascii('value');
> set Composite[ascii('key')]['a@two']=ascii('value');
> It appears DynamicCompositeType does not allow mixing different types of components in the same "position" for the same row, which makes sense, but shouldn't this be a controled error and passed to the client, instead of throwing a fatal exception in the server side?
--
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