[
https://issues.apache.org/jira/browse/BEAM-4519?focusedWorklogId=110299&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-110299
]
ASF GitHub Bot logged work on BEAM-4519:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jun/18 22:04
Start Date: 08/Jun/18 22:04
Worklog Time Spent: 10m
Work Description: axelmagn commented on issue #5582: [BEAM-4519] Add
staging_token to GetManifestRequest
URL: https://github.com/apache/beam/pull/5582#issuecomment-395904289
So I think I've got everything fixed except for regenerating the go protos.
@angoenka did this last time since he's already got the go environment set up,
but I'm having trouble reproducing that environment on my machine. I will
update this thread once I've found a way to move forward with proto generation.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 110299)
Time Spent: 2h (was: 1h 50m)
> Artifact Retrieval Service Protocol should be able to serve multiple
> Manifests.
> -------------------------------------------------------------------------------
>
> Key: BEAM-4519
> URL: https://issues.apache.org/jira/browse/BEAM-4519
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Axel Magnuson
> Assignee: Axel Magnuson
> Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The artifact staging service currently returns a staging_token that can be
> used as a key to access a manifest. However, the current protocol does not
> have a field that accepts this token.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
