[
https://issues.apache.org/jira/browse/BEAM-7084?focusedWorklogId=246797&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246797
]
ASF GitHub Bot logged work on BEAM-7084:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/May/19 15:04
Start Date: 22/May/19 15:04
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-494842957
>(1) An expansion service that produces transforms tagged with the "vanilla"
docker environment but relies on dependencies not in this environment. In my
book, such an expansion service is simply broken and it's not the user's
responsibility to fix it.
What you describe is the current state of the expansion service which always
uses the standard Docker environment. The idea of the PR was to give users the
option to configure the environment. There are more sophisticated ways to
determining the correct environment but I think they are out of scope here.
>(2) An expansion service vending transforms that can be part of a variety
of environments (e.g. subprocess, embedded, or docker) which wants input into
which one the user would prefer (or force?). It's a bit unclear how it would
specify dependencies (artifacts?) in addition, or given an environment how it
would detect that its transforms are compatible with it (absent a fixed list).
If a user has created a dedicated environment for the desired external
transforms, I don't see a reason to prevent him/her from using it. What you are
describing is a more advanced process which we will work out in the discussions
around artifact resolution. We could include additional information about the
environment which would be used by the Expansion Server to compare it against
other environments. Again, the idea here was just to enable use of custom
environments.
----------------------------------------------------------------
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: 246797)
Time Spent: 2.5h (was: 2h 20m)
> 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: 2.5h
> 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)
