[
https://issues.apache.org/jira/browse/BEAM-13629?focusedWorklogId=720353&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-720353
]
ASF GitHub Bot logged work on BEAM-13629:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Feb/22 19:22
Start Date: 03/Feb/22 19:22
Worklog Time Spent: 10m
Work Description: ihji commented on pull request #16490:
URL: https://github.com/apache/beam/pull/16490#issuecomment-1029321024
> Looks pretty good. Left a few comments, but the main thing I'm wondering
about this change is why Dataflow specifically needs this approach. Is this
something we can generalize?
Dataflow uses different artifact retrieval service implementation (worker
built-in) and it currently only supports URL artifact types.
>
> If the other portable runners we expect people to use with Go (Flink,
Spark, and Python Portable) are able to support URL artifacts then maybe we can
instead do this check as part of the existing ResolveArtifactsWithConfig
function.
Yes. We can move this into `ResolveArtifactsWithConfig` after we confirm
that URL artifact type is well supported by the artifact services used by other
portable runners.
--
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 720353)
Time Spent: 2h 20m (was: 2h 10m)
> Update URL artifact type for Dataflow Go
> ----------------------------------------
>
> Key: BEAM-13629
> URL: https://issues.apache.org/jira/browse/BEAM-13629
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow, sdk-go
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: P2
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Update URL artifact type for Dataflow Go
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
