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

ASF GitHub Bot commented on BEAM-1896:
--------------------------------------

GitHub user ssisk opened a pull request:

    https://github.com/apache/beam-site/pull/202

    [BEAM-1896] Add "In-Progress" info to the Built-in I/O Transforms page

    Also added the Apache Hadoop InputFormat to the existing transforms list.
    
    cc @melap 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ssisk/beam-site io-in-progress

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam-site/pull/202.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #202
    
----
commit d96138bf920bfc4c9cc6226173453593581a68c9
Author: Stephen Sisk <[email protected]>
Date:   2017-04-06T15:07:11Z

    Add "In-Progress" info to the Built-in I/O Transforms page

----


> Add list of In Progress IOs to the Pipeline I/O section of the website
> ----------------------------------------------------------------------
>
>                 Key: BEAM-1896
>                 URL: https://issues.apache.org/jira/browse/BEAM-1896
>             Project: Beam
>          Issue Type: Improvement
>          Components: website
>            Reporter: Stephen Sisk
>            Assignee: Stephen Sisk
>
> At https://beam.apache.org/documentation/io/built-in/ we have a list of 
> currently supported IO transforms. 
> It'd be great to add the set of in-progress IO transforms as an additional 
> list on that page. 
> I propose that we should continue to use JIRA as the single source of truth, 
> and this page would just be a convenience to help folks looking to see if an 
> IO might be in the pipeline.Thus, we would manually add any IOs with JIRA 
> issues in that list, and not try to show any status on the page - they can 
> follow a link to the jira issue to find out current status.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to