[ 
https://issues.apache.org/jira/browse/BEAM-4519?focusedWorklogId=110390&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-110390
 ]

ASF GitHub Bot logged work on BEAM-4519:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Jun/18 05:45
            Start Date: 09/Jun/18 05:45
    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-395942269
 
 
   With the help of Ankur, we have regenerated protos.  However I am somewhat 
puzzled by the failing java pre-commit, since the failing task 
(:beam-runners-flink_2.11:compileJava) builds successfully on my machine (and I 
can't find the compile error in the jenkins output).

----------------------------------------------------------------
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: 110390)
    Time Spent: 2h 10m  (was: 2h)

> 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 10m
>  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)

Reply via email to