Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.