You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ahmet Altay (JIRA)" <ji...@apache.org> on 2018/10/03 23:41:00 UTC

[jira] [Commented] (BEAM-5440) Add option to mount a directory inside SDK harness containers

    [ https://issues.apache.org/jira/browse/BEAM-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637621#comment-16637621 ] 

Ahmet Altay commented on BEAM-5440:
-----------------------------------

What is the plan for this JIRA? Are we targeting 2.8.0 with cut date 10/10?

It does not sound like a release blocker.

> Add option to mount a directory inside SDK harness containers
> -------------------------------------------------------------
>
>                 Key: BEAM-5440
>                 URL: https://issues.apache.org/jira/browse/BEAM-5440
>             Project: Beam
>          Issue Type: New Feature
>          Components: java-fn-execution
>            Reporter: Maximilian Michels
>            Priority: Major
>              Labels: portability, portability-flink
>             Fix For: 2.8.0
>
>
> While experimenting with the Python SDK locally, I found it inconvenient that I can't mount a host directory to the Docker containers, i.e. the input must already be in the container and the results of a Write remain inside the container. For local testing, users may want to mount a host directory.
> Since BEAM-5288 the {{Environment}} carries explicit environment information, we could a) add volume args to the {{DockerPayload}}, or b) provide a general Docker arguments field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)