[
https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352172#comment-15352172
]
Ishita Mandhan commented on KAFKA-3522:
---------------------------------------
I'd like to work on this once a consensus has been reached and if this is
something suitable for someone new to kafka (might end up asking a lot of
questions here :) )
[~guozhang] When you say version indicator file, are you thinking of some sort
of file that simply stores the rocksdb version number as a json and perform a
check during startup in KTableStoreSupplier.java? Or a file that stores the
various configurable values (currently hardcoded) in RocksDBStore.java? Or both?
> Consider adding version information into rocksDB storage format
> ---------------------------------------------------------------
>
> Key: KAFKA-3522
> URL: https://issues.apache.org/jira/browse/KAFKA-3522
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Ishita Mandhan
> Labels: architecture
> Fix For: 0.10.1.0
>
>
> Kafka Streams does not introduce any modifications to the data format in the
> underlying Kafka protocol, but it does use RocksDB for persistent state
> storage, and currently its data format is fixed and hard-coded. We want to
> consider the evolution path in the future we we change the data format, and
> hence having some version info stored along with the storage file / directory
> would be useful.
> And this information could be even out of the storage file; for example, we
> can just use a small "version indicator" file in the rocksdb directory for
> this purposes. Thoughts? [~enothereska] [~jkreps]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
