Skip to content

[Bug]: BeamSchema issue #35790

Closed
Closed

Description

@arnavarora2004

What happened?

@derrickaw

There is a problem when trying to assert with beamSchema

  • type: AssertEqual
    config:
    elements:
    - {key: 'row1',
    # Use explicit map syntax to match the actual output
    column_families: {
    cf1: {
    cq1: [
    { value: "value1", timestamp_micros: 5000 }
    ],
    cq2: [
    { value: "value2", timestamp_micros: 1000 }
    ]
    }
    }
    }

in yaml this is converted to:

[{'key': 'row1', 'column_families':
Row(cf1=
Row(cq1=[Row(value='value1', timestamp_micros=5000)],
cq2=[Row(value='value2', timestamp_micros=1000)]))}]

and what I want to assert it with is:

[{'key': 'row1', 'column_families': {'cf1':
{'cq2':
[BeamSchema_165279ce_43e8_4978_9b7b_3524cf48f6e7(value=b'value2', timestamp_micros=1000)],
'cq1':
[BeamSchema_165279ce_43e8_4978_9b7b_3524cf48f6e7(value=b'value1', timestamp_micros=5000)]}}}]

and the assert is incorrect even though the logic in terms of how its supposed to look is correct

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: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Activity

  1. self-assigned this
    on Aug 5, 2025
  2. derrickaw commented on Aug 6, 2025

    @derrickaw
    Collaborator
  3. github-actions commented on Feb 23, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  4. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

  5. added this to the 2.78.0 Release milestone on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions