phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-905) Wrong calculation of maxSetBit in ValueBitSet#or(ImmutableBytesWritable)
Date Tue, 01 Apr 2014 03:21:16 GMT

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

ASF GitHub Bot commented on PHOENIX-905:
----------------------------------------

Github user jtaylor-sfdc commented on the pull request:

    https://github.com/apache/incubator-phoenix/pull/24#issuecomment-39167211
  
    Yes, definitely in 3.0 and 4.0. Perhaps your last change as well, b/c the current plan
is to cut point releases from 3.0 and 4.0 and have master for non compatible type changes.
    
    Would this cause at least 8 bytes worth of data to be serialized? So if you had more than
64 fields, you'd hit a problem? I'd like to understand if this is worthy of sinking the current
RC.


> Wrong calculation of maxSetBit in ValueBitSet#or(ImmutableBytesWritable)
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-905
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-905
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 4.0.0, 5.0.0
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>            Priority: Minor
>             Fix For: 3.0.0, 4.0.0, 5.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message