[
https://issues.apache.org/jira/browse/BEAM-9977?focusedWorklogId=436289&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-436289
]
ASF GitHub Bot logged work on BEAM-9977:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/20 23:52
Start Date: 21/May/20 23:52
Worklog Time Spent: 10m
Work Description: iemejia commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-632402839
Now that this is merged. Can I ask a question. What is the intrinsic
limitation that did not allow old `OffsetRangeTracker` to be refactored for
this use case? or why we want to have both?
Does this mean also that we might need `GrowableBytekeyRangeTracker` and
basically 'dynamic' versions for every `RestrictionTracker` ?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 436289)
Time Spent: 4h 10m (was: 4h)
> Build Kafka Read on top of Java SplittableDoFn
> ----------------------------------------------
>
> Key: BEAM-9977
> URL: https://issues.apache.org/jira/browse/BEAM-9977
> Project: Beam
> Issue Type: New Feature
> Components: io-java-kafka
> Reporter: Boyuan Zhang
> Assignee: Boyuan Zhang
> Priority: P2
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
