You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Apache Beam community maintains different versions of each Load Test. For example, right now, there are two versions of all Python Load Tests: the first one runs on Dataflow runner, and the second one runs on Flink. With the lack of a common place where configuration for the tests can be stored, the configuration is duplicated many times with minimal differences.
The goal is to create a common place for the configuration, so that it could be passed to different files with tests (.test-infra/jenkins/*.groovy) and filtered according to needs.
Imported from Jira BEAM-8941. Original Jira may contain additional context.
Reported by: kamilwu.
Subtask of issue #19221
The text was updated successfully, but these errors were encountered:
The Apache Beam community maintains different versions of each Load Test. For example, right now, there are two versions of all Python Load Tests: the first one runs on Dataflow runner, and the second one runs on Flink. With the lack of a common place where configuration for the tests can be stored, the configuration is duplicated many times with minimal differences.
The goal is to create a common place for the configuration, so that it could be passed to different files with tests (.test-infra/jenkins/*.groovy) and filtered according to needs.
Imported from Jira BEAM-8941. Original Jira may contain additional context.
Reported by: kamilwu.
Subtask of issue #19221
The text was updated successfully, but these errors were encountered: