boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-632408026
> 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?
>
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-631794981
Thanks for your help!
This is an automated message from the Apache Git Service.
To respond to the message,
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-631204566
Run Java PreCommit
This is an automated message from the Apache Git Service.
To respond to the message, please
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-630963389
> > > Should we be using the RangeEndEstimator when providing
progress/splitting for ranges not ending at `Long.MAX_VALUE`?
> > > Lets say the range estimate is bad and is
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-630952259
> Should we be using the RangeEndEstimator when providing progress/splitting
for ranges not ending at `Long.MAX_VALUE`?
>
> Lets say the range estimate is bad and is
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-630536199
Latest changes are for addressing comments and using double during
computation. @lukecwik PTAL. Thanks for your help!
boyuanzz commented on pull request #11715:
URL: https://github.com/apache/beam/pull/11715#issuecomment-629344196
R: @lukecwik
CC: @robertwb
This is an automated message from the Apache Git Service.
To respond to the
