[
https://issues.apache.org/jira/browse/SAMZA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173869#comment-14173869
]
Chris Riccomini commented on SAMZA-431:
---------------------------------------
I think we mean "wiring" as it pertains to dependency injection. Given your
options, the factory one. Basically, it's annoying to have to write
org.apache.samza.foo.Bar a bunch of times in the config.
It kind of feels like we're bouncing all over the place right now: SAMZA-346
(ConfigStream), several global state tickets (SAMZA-353, SAMZA-402, SAMZA-424),
and config re-write (SAMZA-40, SAMZA-431). I'm happy we're thinking through our
design decisions, but it's starting to feel like we're doing too much.
With that in mind, I propose that we back off on this ticket, and just focus on
some of the "easy win" work in SAMZA-40 (validating config, doc generation from
config, config defaults, and removing implicits). I'd also propose that we
follow through on SAMZA-348. I think if we do these things, we'd be in pretty
good shape, and the changes wouldn't be too drastic.
Thoughts?
> Separate wiring from the configuration system
> ---------------------------------------------
>
> Key: SAMZA-431
> URL: https://issues.apache.org/jira/browse/SAMZA-431
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.8.0
> Reporter: Chinmay Soman
> Fix For: 0.8.0
>
>
> Currently, we're mixing wiring together with config. Investigate how this can
> be simplified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
