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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
