[
https://issues.apache.org/jira/browse/SAMZA-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Kumarasubramanian updated SAMZA-2790:
---------------------------------------------
Description:
Runloop currently takes in lot of parameters and the constructor has grown to
the point where it is unmanageable with multiple overloads. Introducing new
configuration requires lot of updates to existing tests and components even if
the parameters have no effect on all of the usages.
With this PR, we should be able to decouple different users of RunLoop and
enable these components to have their own scoped config. e.g.,
{{SideInputManager}} can now have its own set of runloop parameters without
having to tie itself with {{TaskConfig}}
> Cleanup RunLoop constructor explosion
> -------------------------------------
>
> Key: SAMZA-2790
> URL: https://issues.apache.org/jira/browse/SAMZA-2790
> Project: Samza
> Issue Type: Improvement
> Reporter: Bharath Kumarasubramanian
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Runloop currently takes in lot of parameters and the constructor has grown to
> the point where it is unmanageable with multiple overloads. Introducing new
> configuration requires lot of updates to existing tests and components even
> if the parameters have no effect on all of the usages.
> With this PR, we should be able to decouple different users of RunLoop and
> enable these components to have their own scoped config. e.g.,
> {{SideInputManager}} can now have its own set of runloop parameters without
> having to tie itself with {{TaskConfig}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
