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] [Comment Edited] (CASSANDRA-8375) Cleanup of generics in bounds serialization
Date Tue, 10 Mar 2015 08:21:38 GMT

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

Branimir Lambov edited comment on CASSANDRA-8375 at 3/10/15 8:21 AM:
---------------------------------------------------------------------

Java 8 accepts it, 7 doesn't. Updated.

Apologies, I have no excuse for these blunders.


was (Author: blambov):
Java 7 accepts it, 6 doesn't. Updated.

Apologies, I have no excuse for these blunders.

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