Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Mon, 11 Sep 2017 16:18:00 +0000 (UTC)
From: "Henning Korsholm Rohde (JIRA)" <jira@apache.org>
To: commits@beam.apache.org
Message-ID: <JIRA.13101311.1505146672000.80349.1505146680572@Atlassian.JIRA>
In-Reply-To: <JIRA.13101311.1505146672000@Atlassian.JIRA>
References: <JIRA.13101311.1505146672000@Atlassian.JIRA> <JIRA.13101311.1505146672245@jira-lw-us.apache.org>
Subject: [jira] [Created] (BEAM-2876) Add provision api proto
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Sep 2017 16:18:06 -0000

Henning Korsholm Rohde created BEAM-2876:
--------------------------------------------

             Summary: Add provision api proto
                 Key: BEAM-2876
                 URL: https://issues.apache.org/jira/browse/BEAM-2876
             Project: Beam
          Issue Type: Sub-task
          Components: beam-model
            Reporter: Henning Korsholm Rohde
            Assignee: Henning Korsholm Rohde


As per discussion in https://s.apache.org/beam-fn-api-container-contract, we need to define the provision API to allow boot code access to pipeline options, in particular.

It is proposed as a separate API instead of merging it with control or artifact:
   (1) Not merging with control avoids having the boot code talk to control, only to disconnect and have the SDK harness connect. The runner can't then use the lifetime of the connection to be the lifetime of the SDK harness.
   (2) Not merging with artifact allows for simple, reusable artifact proxies.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)