You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2018/11/07 09:08:00 UTC

[jira] [Resolved] (BEAM-5974) Migrate ByteKeyRangeTracker to use tryClaim(ByteKey.EMPTY) as end of range claim instead of markDone

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

Ismaël Mejía resolved BEAM-5974.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.9.0

> 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
>             Fix For: 2.9.0
>
>          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)