[
https://issues.apache.org/jira/browse/KAFKA-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074752#comment-17074752
]
Richard Yu commented on KAFKA-9808:
-----------------------------------
My assumption is that to make this refactoring more doable, we probably can
break the issue down, and tackle the basic store types, one at a time:
# KeyValueStore
# SessionStore
# WindowStore
# SegmentedBytesStore
Not all of them I suppose would require extensive cleanup, but its good to keep
in mind,.
> Refactor State Store Hierarchy
> ------------------------------
>
> Key: KAFKA-9808
> URL: https://issues.apache.org/jira/browse/KAFKA-9808
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Richard Yu
> Priority: Major
> Attachments: Current State Store Hierarchy.pdf
>
>
> Over years of development, Kafka contributors has been adding more and more
> state store classes on top of each other without too much regard to making it
> more approachable for future modifications. For instance, it has become
> increasingly difficult to add new API to state store classes while at the
> same time, preventing them from being exposed to users.
> In sum, the entire hierarchy is slowly spiraling out of control, and there is
> a growing need to consolidate the multiple state store types into a few more
> manageable ones for future Kafka developers.
> Note: There has already been a couple of attempts to simplify the state store
> hierarchy, but while the task isn't too complex, its just the enormous scope
> of the change which makes things difficult.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
