[
https://issues.apache.org/jira/browse/BEAM-11354?focusedWorklogId=518089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-518089
]
ASF GitHub Bot logged work on BEAM-11354:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Nov/20 19:16
Start Date: 30/Nov/20 19:16
Worklog Time Spent: 10m
Work Description: robertwb commented on pull request #13431:
URL: https://github.com/apache/beam/pull/13431#issuecomment-735986540
I've updated the documentation.
Java provides meaning to these specific methods by using annotations, but I
still think we want a type in Python (unless we wanted to make *all* DoFns into
RestrictionProviders and WatermarkEstimatorProviders, with their corresponding
default methods). Not being able to bind these things based on DoFn properties
is very constraining though (as you discovered as well).
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 518089)
Time Spent: 1h 10m (was: 1h)
> Allow Splittable DoFn itself to be used as the restriction provider.
> ---------------------------------------------------------------------
>
> Key: BEAM-11354
> URL: https://issues.apache.org/jira/browse/BEAM-11354
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: Robert Bradshaw
> Priority: P2
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Binding the provider to the DoFn class itself at construction time can be
> limiting, we should add an option to use the DoFn instance itself as the
> restriction provider.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
