[
https://issues.apache.org/jira/browse/BEAM-10670?focusedWorklogId=599938&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-599938
]
ASF GitHub Bot logged work on BEAM-10670:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 20/May/21 17:44
Start Date: 20/May/21 17:44
Worklog Time Spent: 10m
Work Description: boyuanzz commented on pull request #14801:
URL: https://github.com/apache/beam/pull/14801#issuecomment-845327802
Sorry that I misunderstood the execution of `Transform.expand()`. The
transform expansion happens during applying a PTransform to a certain
PCollection before we calling `runner.run(pipeline)`. So populating experiments
doesn't work for our need. Another way I'm thinking about is to have KafkaIO
run expansion based on the given runner. It can be done via checking runner
class prefix.
--
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: 599938)
Time Spent: 46h 20m (was: 46h 10m)
> Make non-portable Splittable DoFn the only option when executing Java "Read"
> transforms
> ---------------------------------------------------------------------------------------
>
> Key: BEAM-10670
> URL: https://issues.apache.org/jira/browse/BEAM-10670
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Luke Cwik
> Assignee: Ismaël Mejía
> Priority: P1
> Labels: Clarified
> Fix For: 2.30.0
>
> Time Spent: 46h 20m
> Remaining Estimate: 0h
>
> All runners seem to be capable of migrating to splittable DoFn for
> non-portable execution except for Dataflow runner v1 which will internalize
> the current primitive read implementation that is shared across runner
> implementations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
