Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Beam YAML provider parsing breakage #31970

Closed
1 of 17 tasks
Polber opened this issue Jul 24, 2024 · 0 comments · Fixed by #31974
Closed
1 of 17 tasks

[Bug]: Beam YAML provider parsing breakage #31970

Polber opened this issue Jul 24, 2024 · 0 comments · Fixed by #31974
Labels
bug P0 yaml
Milestone
2.59.0 Release

Comments

@Polber
Copy link
Contributor

Polber commented Jul 24, 2024

What happened?

#31604 added a new syntax for declaring a provider through an external file.

  1. The schema validation will fail for any provider inlined on a YAML pipeline.
  2. With schema validation fixed, merging providers incorrectly parses provider metadata as transforms (__uuid__ and __line__)

Issue Priority

Priority: 0 (outage / urgent vulnerability)

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug P0 yaml
Projects
None yet
Milestone
2.59.0 Release
Development

Successfully merging a pull request may close this issue.

[yaml] Fix yaml provider schema validation and merging Polber/beam
2 participants
@jrmccluskey @Polber