[
https://issues.apache.org/jira/browse/KAFKA-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-555.
-----------------------------
Resolution: Duplicate
Assignee: Jay Kreps
Did it.
> Add a key-based log retention strategy
> --------------------------------------
>
> Key: KAFKA-555
> URL: https://issues.apache.org/jira/browse/KAFKA-555
> Project: Kafka
> Issue Type: New Feature
> Reporter: Jay Kreps
> Assignee: Jay Kreps
>
> Currently we have two log retention strategies: one based on time and one
> based on log size. These work well for "event" type data--i.e. data that
> consists only of appends. However if the events model changes to an
> underlying keyed data set, a more convenient retention strategy would delete
> keys that had been overwritten rather than retaining whole segments.
> The proposed implementation would be a background process that scanned log
> segments and recopied only keys that hadn't been overwritten. Some more
> details are in this wiki:
> https://cwiki.apache.org/confluence/display/KAFKA/Keyed+Messages+Proposal
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
