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.

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

[Bug]: ItFramework PipelineUtils createJobName and extractJobName not align #29875

Closed
16 tasks
Abacn opened this issue Dec 27, 2023 · 0 comments · Fixed by #29876
Closed
16 tasks

[Bug]: ItFramework PipelineUtils createJobName and extractJobName not align #29875

Abacn opened this issue Dec 27, 2023 · 0 comments · Fixed by #29876
Assignees
Labels

Comments

@Abacn
Copy link
Contributor

Abacn commented Dec 27, 2023

What happened?

extractJobName is intended to inverse createJobName which append a timestamp and some random chars from the input job name. However, in the latest release validation it is found the reported pipeline name and labels (which relies on extractJobName) is not correct.

https://github.com/apache/beam/blob/master/it/common/src/test/java/org/apache/beam/it/common/utils/PipelineUtilsTest.java has tests on testCreateExtractJobName() without random character, but not the case with random character. Likely some later change on the API has broken this alignment.

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: 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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant