You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2015/04/07 02:39:14 UTC
[jira] [Assigned] (PHOENIX-1686) Data length should be checked in
KeyValueSchema.next() and maxOffset should be set correctly by the caller
[ https://issues.apache.org/jira/browse/PHOENIX-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maryann Xue reassigned PHOENIX-1686:
------------------------------------
Assignee: Maryann Xue
> 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
> Assignee: 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)