beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4519) Artifact Retrieval Service Protocol should be able to serve multiple Manifests.
Date Fri, 08 Jun 2018 17:05:00 GMT


ASF GitHub Bot logged work on BEAM-4519:

                Author: ASF GitHub Bot
            Created on: 08/Jun/18 17:04
            Start Date: 08/Jun/18 17:04
    Worklog Time Spent: 10m 
      Work Description: bsidhom commented on a change in pull request #5582: [BEAM-4519] Add
staging_token to GetManifestRequest

 File path: model/job-management/src/main/proto/beam_artifact_api.proto
 @@ -81,7 +81,11 @@ message ProxyManifest {
 // A request to get the manifest of a Job.
-message GetManifestRequest {}
+message GetManifestRequest {
+  // (Required) An opaque token representing the entirety of the staged artifacts.
 Review comment:
   FYI, this will need to be added to `JobInfo` in order to plumb this all the way through
the workers. It also looks like you'll need to rebase #5584 with the rename.

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:

Issue Time Tracking

    Worklog Id:     (was: 110164)
    Time Spent: 1h 40m  (was: 1.5h)

> Artifact Retrieval Service Protocol should be able to serve multiple Manifests.
> -------------------------------------------------------------------------------
>                 Key: BEAM-4519
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Axel Magnuson
>            Assignee: Axel Magnuson
>            Priority: Minor
>          Time Spent: 1h 40m
>  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

View raw message