[
https://issues.apache.org/jira/browse/BEAM-4290?focusedWorklogId=106924&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-106924
]
ASF GitHub Bot logged work on BEAM-4290:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/May/18 23:09
Start Date: 29/May/18 23:09
Worklog Time Spent: 10m
Work Description: angoenka commented on a change in pull request #5489:
[BEAM-4290] proto changes to support artifact_staging_id
URL: https://github.com/apache/beam/pull/5489#discussion_r191601617
##########
File path: model/job-management/src/main/proto/beam_artifact_api.proto
##########
@@ -102,13 +99,19 @@ message ArtifactChunk {
bytes data = 1;
}
+message PutArtifactMetadata {
+ // (Required) An identifier for artifact staging session.
+ string artifact_staging_id = 1;
Review comment:
I agree the name seems to be very similar but artifact_staging_id and
staging_token are fundamentally different.
artifact_staging_id defines and id to stage token with. This id is generated
by JobService. This id can define some meta data to about the artifact like
jobId, staging dir etc.
staging_token is a token used to retrieve staged token by
ArtifactRetrivalService. This token is generated by ArtifactStagingService.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 106924)
Time Spent: 1h 20m (was: 1h 10m)
> ArtifactStagingService that stages to a distributed filesystem
> --------------------------------------------------------------
>
> Key: BEAM-4290
> URL: https://issues.apache.org/jira/browse/BEAM-4290
> Project: Beam
> Issue Type: Sub-task
> Components: runner-core
> Reporter: Eugene Kirpichov
> Assignee: Ankur Goenka
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Using the job's staging directory from PipelineOptions.
> Physical layout on the distributed filesystem is TBD but it should allow for
> arbitrary filenames and ideally for eventually avoiding uploading artifacts
> that are already there.
> Handling credentials is TBD.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
