[ 
https://issues.apache.org/jira/browse/BEAM-5974?focusedWorklogId=163383&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-163383
 ]

ASF GitHub Bot logged work on BEAM-5974:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Nov/18 08:53
            Start Date: 07/Nov/18 08:53
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on issue #6949: [BEAM-5974] Fix 
ByteKeyRangeTracker to handle tryClaim(ByteKey.EMPTY) instead of exposing 
markDone
URL: https://github.com/apache/beam/pull/6949#issuecomment-436550243
 
 
   Sorry a bit late for this review, Is there any consequence on this and the 
previous change in the logic of the other ByteKeyRangeTracker 
(`org.apache.beam.sdk.io.range.ByteKeyRangeTracker`) ?

----------------------------------------------------------------
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: 163383)
    Time Spent: 2.5h  (was: 2h 20m)

> Migrate ByteKeyRangeTracker to use tryClaim(ByteKey.EMPTY) as end of range 
> claim instead of markDone
> ----------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-5974
>                 URL: https://issues.apache.org/jira/browse/BEAM-5974
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-hbase, sdk-java-core
>    Affects Versions: 2.8.0
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: Major
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> org.apache.beam.sdk.transforms.splittabledofn.ByteKeyRangeTracker doesn't 
> handle tryClaim(ByteKey.EMPTY) and the related doneness check or 
> checkpointing since doneness checking can't handle the empty interval, 
> checkpointing returns invalid checkpoints or errors out since it is using the 
> lastClaimedKey vs the lastAttemptedKey for doneness checking



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to