Skip to content

[Bug]: Profiler instrumentation ignores profiler-related options on portable runners #39613

Closed

Description

@tvalentyn

What happened?

Portable runner and Dataflow runner appear to have different ways of passing pipeline options to the SDK harness when the SDK boots.

Current parsing of profiler options only works on Dataflow runner. We should fix this and provide a more convenient and universal helpers to use in the boot entrypoint to deal with the pipeline options.

Issue Priority

Priority: 2 (default / most bugs 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: Prism Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Activity

  1. self-assigned this
    on Aug 4, 2026
  2. added this to the 2.77.0 Release milestone on Aug 7, 2026
  3. tvalentyn commented on Aug 11, 2026

    @tvalentyn
    ContributorAuthor

    this should be fixed in the next release (2.77.0) , but if anyone needs the fix earlier, most likely one can fish out beam's boot.go from the Apache Beam 2.77.0.dev (nightly) image and superimpose that onto 2.75.0/2.76.0 image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions