[BEAM-14515] Decouple interactive Beam from Jupyter

• Type: Improvement
• Status: Open
• Priority: P2
• Resolution: Unresolved
• Component/s: runner-py-interactive
• Assignee: Unassigned
• Reporter: Brian Hulette
• Created: 25/May/22 23:37
• Updated: 05/Jun/22 00:30

Description

Some aspects of interactive Beam (e.g. triggering execution with ib.collect) make sense to use outside of a Jupyter notebook. We should make sure that use-cases like this are possible, and we only require a notebook if it's actually necessary. In my mind that should just be features that are explicitly integrating with Jupyter, like side panels, custom magics, etc...

Things like caching and plotting tools even make sense to use outside of Jupyter (a plotting tool can return a handle that the user could use to save the plot as an image).

Issue Links

• relates to: BEAM-14211 Add "interactive" DataFrame operations that eagerly trigger execution