[ 
https://issues.apache.org/jira/browse/BEAM-8233?focusedWorklogId=314722&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-314722
 ]

ASF GitHub Bot logged work on BEAM-8233:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Sep/19 23:17
            Start Date: 18/Sep/19 23:17
    Worklog Time Spent: 10m 
      Work Description: ibzib commented on issue #9605: [BEAM-8233] [BEAM-8214] 
[BEAM-8232] Document environment_type flag
URL: https://github.com/apache/beam/pull/9605#issuecomment-532902618
 
 
   R: @soyrice 
   
   I saw you were working on container documentation, so I wanted to sync up on 
this.
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 314722)
    Time Spent: 0.5h  (was: 20m)

> Separate loopback and docker modes on Flink runner guide
> --------------------------------------------------------
>
>                 Key: BEAM-8233
>                 URL: https://issues.apache.org/jira/browse/BEAM-8233
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink, website
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Running loopback should be the "getting started" option, and docker mode 
> should be an "advanced" option with its own section of the Flink runner guide 
> with instructions and explanations (you need to build the docker container 
> images, you can't see your output in a local filesystem without 
> workarounds..) [https://beam.apache.org/documentation/runners/flink/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to