[
https://issues.apache.org/jira/browse/BEAM-5487?focusedWorklogId=147294&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-147294
]
ASF GitHub Bot logged work on BEAM-5487:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Sep/18 20:34
Start Date: 24/Sep/18 20:34
Worklog Time Spent: 10m
Work Description: lukecwik commented on issue #6481: [BEAM-5487]
ByteKeyRangeTracker restrictions do not cover the entire interval because of
incorrect next key
URL: https://github.com/apache/beam/pull/6481#issuecomment-424115474
R: @iemejia
CC: @chamikaramj
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 147294)
Time Spent: 20m (was: 10m)
> ByteKeyRangeTracker restrictions do not cover the entire interval because of
> incorrect next key
> -----------------------------------------------------------------------------------------------
>
> Key: BEAM-5487
> URL: https://issues.apache.org/jira/browse/BEAM-5487
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Luke Cwik
> Assignee: Luke Cwik
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The definition of next for a byte key is incorrectly set as old key + 1 when
> treating the key as the next largest value, for example
> 0x01 is the next key for 0x00
>
> The ByteKey compareTo operator treats two keys where one key is the proper
> prefix of the other as smaller hence 0x01 is greater then 0x00, but so is
> 0x0000 thus next is skipping over 0x0000 as the next smallest key larger then
> 0x00.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
