kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishita Mandhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format
Date Mon, 22 Aug 2016 17:51:20 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431288#comment-15431288
] 

Ishita Mandhan commented on KAFKA-3522:
---------------------------------------

Just wanted to check in to see if now is a good time to bring this back up. I'm looking for
some small feature in streams to work on so if there's some other minor feature that you'd
rather me divert my attention to at the moment, that's fine too :)

> 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)

Mime
View raw message