[
https://issues.apache.org/jira/browse/BEAM-7084?focusedWorklogId=246668&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246668
]
ASF GitHub Bot logged work on BEAM-7084:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/May/19 11:00
Start Date: 22/May/19 11:00
Worklog Time Spent: 10m
Work Description: robertwb commented on issue #8639: [BEAM-7084] Allow
custom environments for external transforms
URL: https://github.com/apache/beam/pull/8639#issuecomment-494755279
Yes, we could add extra environments to the proto.
It feels like this is working around the core issue that expansion services
should be responsible for specifying their environments. If the non-standard
environment is preferred, possibly this should be done as part of starting up
the expansion service.
----------------------------------------------------------------
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: 246668)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
