phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-1686) Data length should be checked in KeyValueSchema.next() and maxOffset should be set correctly by the caller
Date Tue, 07 Apr 2015 00:39:14 GMT

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

Maryann Xue resolved PHOENIX-1686.
----------------------------------
    Resolution: Fixed

> Data length should be checked in KeyValueSchema.next() and maxOffset should be set correctly
by the caller
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1686
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1686
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.2.0
>            Reporter: Maryann Xue
>            Priority: Minor
>             Fix For: 4.3.0
>
>         Attachments: 1686.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When decoding values from a KeyValueSchema data object, we should check that the length
specified (either by its type of fixed length or by the length flag) does not exceed maxOffset.
> Meanwhile, maxOffset should not be the total length of the ImmutableBytesWritable object,
but instead should be the total length minus the length of the tailing valueSetBit.



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

Mime
View raw message