[
https://issues.apache.org/jira/browse/BEAM-11997?focusedWorklogId=687367&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-687367
]
ASF GitHub Bot logged work on BEAM-11997:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Nov/21 15:23
Start Date: 29/Nov/21 15:23
Worklog Time Spent: 10m
Work Description: MiguelAnzoWizeline commented on pull request #15549:
URL: https://github.com/apache/beam/pull/15549#issuecomment-981738832
Hi, the problem I'm having with that kind of approach is that we cannot get
a closest valid redis cursor, as we don't know what the next cursor is going to
be until we send the actual cursor to redis. Obtaining a calculated cursor and
sending it to redis would cause redis to return us a wrong cursor for the data
we are trying to obtain.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 687367)
Time Spent: 7h 40m (was: 7.5h)
> 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: 7h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
