[ https://issues.apache.org/jira/browse/BEAM-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Kang updated BEAM-7926: ---------------------------- Description: Support auto plotting / charting of materialized data of a given PCollection with Interactive Beam. Say an Interactive Beam pipeline defined as {code:java} p = beam.Pipeline(InteractiveRunner()) pcoll = p | 'Transform' >> transform() pcoll2 = ... pcoll3 = ...{code} The use can call a single function and get auto-magical charting of the data. e.g., {code:java} show(pcoll, pcoll2) {code} Throughout the process, a pipeline fragment is built to include only transforms necessary to produce the desired pcolls (pcoll and pcoll2) and execute that fragment. This makes the Interactive Beam user flow data-centric. Detailed [design|[https://docs.google.com/document/d/1DYWrT6GL_qDCXhRMoxpjinlVAfHeVilK5Mtf8gO6zxQ/edit#heading=h.v6k2o3roarzz]]. was: Support auto plotting / charting of materialized data of a given PCollection with Interactive Beam. Say an Interactive Beam pipeline defined as {code:java} p = beam.Pipeline(InteractiveRunner()) pcoll = p | 'Transform' >> transform() pcoll2 = ... pcoll3 = ...{code} The use can call a single function and get auto-magical charting of the data. e.g., {code:java} show(pcoll, pcoll2) {code} Throughout the process, a pipeline fragment is built to include only transforms necessary to produce the desired pcolls (pcoll and pcoll2) and execute that fragment. This makes the Interactive Beam user flow data-centric. > Show PCollection with Interactive Beam in a data-centric user flow > ------------------------------------------------------------------ > > Key: BEAM-7926 > URL: https://issues.apache.org/jira/browse/BEAM-7926 > Project: Beam > Issue Type: New Feature > Components: runner-py-interactive > Reporter: Ning Kang > Assignee: Ning Kang > Priority: Major > Time Spent: 19h 50m > Remaining Estimate: 0h > > Support auto plotting / charting of materialized data of a given PCollection > with Interactive Beam. > Say an Interactive Beam pipeline defined as > > {code:java} > p = beam.Pipeline(InteractiveRunner()) > pcoll = p | 'Transform' >> transform() > pcoll2 = ... > pcoll3 = ...{code} > The use can call a single function and get auto-magical charting of the data. > e.g., > {code:java} > show(pcoll, pcoll2) > {code} > Throughout the process, a pipeline fragment is built to include only > transforms necessary to produce the desired pcolls (pcoll and pcoll2) and > execute that fragment. > This makes the Interactive Beam user flow data-centric. > > Detailed > [design|[https://docs.google.com/document/d/1DYWrT6GL_qDCXhRMoxpjinlVAfHeVilK5Mtf8gO6zxQ/edit#heading=h.v6k2o3roarzz]]. -- This message was sent by Atlassian Jira (v8.3.4#803005)