[
https://issues.apache.org/jira/browse/BEAM-7084?focusedWorklogId=246737&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246737
]
ASF GitHub Bot logged work on BEAM-7084:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/May/19 14:02
Start Date: 22/May/19 14:02
Worklog Time Spent: 10m
Work Description: mxm commented on issue #8639: [BEAM-7084] Allow custom
environments for external transforms
URL: https://github.com/apache/beam/pull/8639#issuecomment-494816099
I agree, setting up the environment up front on the Expansion Service is
definitely an option. I think that an additional configuration of the preferred
expansion environment via the pipeline options would be desirable for the user,
who can already do that for the main environment of the pipeline.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 246737)
Time Spent: 1h 10m (was: 1h)
> Support custom environment types when expanding external transforms
> -------------------------------------------------------------------
>
> Key: BEAM-7084
> URL: https://issues.apache.org/jira/browse/BEAM-7084
> Project: Beam
> Issue Type: Bug
> Components: beam-model, sdk-java-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Labels: portability
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The {{ExpansionService}} registers a default Docker JAVA SDK environment.
> Users should be able to specify other types of environment, i.e.
> Process/External/Embedded.
> We can add an {{environment_type}} field to the {{ExpansionRequest}} Proto
> message.
> CC [~robertwb]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
