You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2024/02/19 21:37:00 UTC
[jira] [Created] (KAFKA-16279) Avoid leaking abstractions of `StateStore`
Matthias J. Sax created KAFKA-16279:
---------------------------------------
Summary: Avoid leaking abstractions of `StateStore`
Key: KAFKA-16279
URL: https://issues.apache.org/jira/browse/KAFKA-16279
Project: Kafka
Issue Type: Improvement
Components: streams
Reporter: Matthias J. Sax
The `StateStore` interface is user facing and contains a few life-cycle management methods (like `init()` and `close()`) – those methods are exposed for users to develop custom state stores.
However, we also use `StateStore` as base interface for store-handles in the PAPI, and thus life-cycle management methods are leaking into the PAPI (maybe also others – would need a dedicated discussion which one we consider useful for PAPI users and which not).
We should consider to change what we expose in the PAPI (atm, we only document via JavaDocs that eg. `close()` should never be called; but it's of course not ideal and would be better if `close()` et al. would not be expose for `PAPI` users to begin with.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)