Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Break DynamicSpout, KafkaConsumer, and SidelineSpout into separate modules #19

Open
Crim opened this issue Oct 18, 2017 · 2 comments
Open

Comments

@Crim
Copy link
Contributor

Crim commented Oct 18, 2017

To provide clear separation of concerns between the DynamicSpout framework, the 'Sideline Spout' implementation, and the 'Kafka' consumer implementation, we should separate these out into maven modules.

@Crim Crim added this to the 0.9.0 milestone Oct 18, 2017
@stanlemon
Copy link
Contributor

@Crim I feel like the 0.9 milestone is a bit ambition, can we focus on production-readiness in 0.9 and concentrate more splitting in 0.10?

@Crim Crim removed this from the 0.9.0 milestone Oct 21, 2017
This was referenced Nov 21, 2017
@Crim
Copy link
Contributor Author

Crim commented Nov 24, 2017

I think after #65 the only remaining blocker for this is SpoutConfig contains a reference to Kafka Consumer to set the default consumer class. That would need to be removed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants