cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8375) Cleanup of generics in bounds serialization
Date Fri, 06 Mar 2015 12:13:38 GMT

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

Branimir Lambov updated CASSANDRA-8375:
---------------------------------------
    Attachment: 8375-v3.patch

Oops, raw Range type fooled both the compiler and me. Fixed and checked for other raw uses
of bounds and ranges.

> Cleanup of generics in bounds serialization
> -------------------------------------------
>
>                 Key: CASSANDRA-8375
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8375
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Branimir Lambov
>            Assignee: Branimir Lambov
>            Priority: Trivial
>             Fix For: 3.0
>
>         Attachments: 8375-v2.patch, 8375-v3.patch, 8375.patch
>
>
> There is currently a single serializer for {{AbstractBounds}} applied to both {{Token}}
and {{RowPosition}} ranges and bounds. This serializer does not know which kind of bounds
it needs to work with, which causes some necessarily unsafe conversions and needs extra code
in all bounds types ({{toRowBounds}}/{{toTokenBounds}}) to make the conversions safe, the
application of which can be easily forgotten.
> As all users of this serialization know in advance the kind of range they want to serialize,
this can be replaced by simpler type-specific serialization.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message