[
https://issues.apache.org/jira/browse/KAFKA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300251#comment-14300251
]
Jay Kreps commented on KAFKA-1910:
----------------------------------
I guess the real question is how to slice it up. Big classes aren't great but
bad abstractions are worse.
One thought I had had was that maybe we could somehow factor out a kind of
ConsumerCoordinator class that would manage the interaction with the
coordinator--heartbeat, groups, etc. But the hard part is figuring out the
boundaries of that abstraction...
> Refactor KafkaConsumer
> ----------------------
>
> Key: KAFKA-1910
> URL: https://issues.apache.org/jira/browse/KAFKA-1910
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
>
> KafkaConsumer now contains all the logic on the consumer side, making it a
> very huge class file, better re-factoring it to have multiple layers on top
> of KafkaClient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
