[jira] [Work logged] (BEAM-11997) Implement RedisIO on top of Splittable DoFn

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 03/Nov/21 15:55
            Start Date: 03/Nov/21 15:55
    Worklog Time Spent: 10m 
      Work Description: MiguelAnzoWizeline commented on pull request #15549:
URL: https://github.com/apache/beam/pull/15549#issuecomment-959539363


   Hi @lukecwik 
   I'm working on the changes mentioned, I have one question, if I decide to use the ByteKeyRangeTracker instead of the new RedisCursorRangeTracker that I was implementing, how would updating the range work? would I need to update the range to [nextCursor, end] after every loop? If so, would that be done by creating a new instance of the tracker with the updated range in every loop? and in that case would the end restriction is going to always be 0?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 674706)
    Time Spent: 3h 20m  (was: 3h 10m)

> Implement RedisIO on top of Splittable DoFn
> -------------------------------------------
>
>                 Key: BEAM-11997
>                 URL: https://issues.apache.org/jira/browse/BEAM-11997
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-redis
>            Reporter: Boyuan Zhang
>            Assignee: Miguel Anzo
>            Priority: P2
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)