apache/beam

[Task]: Update Python slowly updating side input example

Open

#35,935 opened on Aug 21, 2025

View on GitHub
 (21 comments) (0 reactions) (6 assignees)Java (4,097 forks)batch import
P2good first issuepythontaskwebsite

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 7d 20h) (227 merged PRs in 30d)

Description

What needs to happen?

https://beam.apache.org/documentation/patterns/side-inputs/ is missing a side input pattern for Python

When doing this, we should factor in https://github.com/apache/beam/issues/35934 (and probably use Latest.Globally.without_defaults() and test on Dataflow)

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Contributor guide

Research direction
Implement the missing Python side input pattern on the website documentation, referencing issue #35934 and using Latest.Globally.without defaults(). Test on Dataflow.
Tech stack
python
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonApache Beam
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65