[
https://issues.apache.org/jira/browse/BEAM-8815?focusedWorklogId=353936&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-353936
]
ASF GitHub Bot logged work on BEAM-8815:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Dec/19 00:20
Start Date: 05/Dec/19 00:20
Worklog Time Spent: 10m
Work Description: lukecwik commented on pull request #10285: [BEAM-8815]
Define the no artifacts retrieval token in proto
URL: https://github.com/apache/beam/pull/10285#discussion_r354053905
##########
File path: model/job-management/src/main/proto/beam_artifact_api.proto
##########
@@ -67,6 +69,10 @@ message ArtifactMetadata {
// A collection of artifacts.
message Manifest {
+ enum Constants {
Review comment:
The proto code generator will place enums into the root namespace and not
use the name of the enum as a namespace for some languages while in other
languages like Java the enum's name is part of the namespace which is why they
are wrapped inside a message.
I ran into this issue with the enums which used the same constant
`UNSPECIFIED` in the cases where the enums were defined at the root level of
the proto.
----------------------------------------------------------------
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: 353936)
Time Spent: 4h 40m (was: 4.5h)
> Portable pipeline execution without artifact staging
> ----------------------------------------------------
>
> Key: BEAM-8815
> URL: https://issues.apache.org/jira/browse/BEAM-8815
> Project: Beam
> Issue Type: Task
> Components: runner-core, runner-flink
> Affects Versions: 2.17.0
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: portability
> Fix For: 2.17.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> The default artifact staging implementation relies on a distributed
> filesystem. A directory and manifest will be created even when artifact
> staging isn't used, and the container boot code will fail retrieving
> artifacts, even though there are non. In a containerized environment it is
> common to package artifacts into containers. It should be possible to run the
> pipeline w/o a distributed filesystem.
> [https://lists.apache.org/thread.html/1b0d545955a80688ea19f227ad943683747b17beb45368ad0908fd21@%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
