cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-4992) TTL/WRITETIME function against collection column returns invalid value
Date Mon, 26 Nov 2012 15:02:57 GMT
Yuki Morishita created CASSANDRA-4992:
-----------------------------------------

             Summary: TTL/WRITETIME function against collection column returns invalid value
                 Key: CASSANDRA-4992
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4992
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.0 beta 2
            Reporter: Yuki Morishita
            Priority: Minor


Since we cannot query individual content of collection in 1.2, TTL/WRITETIME function on collection
column does not make sense. But currently we can perform those function on collection and
get deserialization error like:

{code}
value '\x00\x03\x00\x01c\x00\x01b\x00\x01a' (in col 'writetime(l)') can't be deserialized
as bigint: unpack requires a string argument of length 8
{code}

Looks like it tries to deserialize whole list/set/map content as bigint for WRITETIME and
int for TTL.

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