damccorm opened a new issue, #19660:
URL: https://github.com/apache/beam/issues/19660

   LoadTestBuilder contains some sdk specific logic inside it's methods ("if"'s 
depending on sdk specific field names, sdk specific pipeline options format, 
etc).
   
   How we could mitigate that: 
    - Have common pojos representing all necessary parameters holding all 
options/job parameters in the same fields.
    - Have one logic for all the operations and split it to more atomic 
operations. 
    - Build options at the end to SDK specific representations.
   
   Imported from Jira 
[BEAM-7539](https://issues.apache.org/jira/browse/BEAM-7539). Original Jira may 
contain additional context.
   Reported by: ŁukaszG.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to