[
https://issues.apache.org/jira/browse/KAFKA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438975#comment-13438975
]
Swapnil Ghike commented on KAFKA-475:
-------------------------------------
Jun: Thanks for pointing out the mistake. I could not see why (a) in your
suggestions is important though. Could you please elaborate if it makes a
difference if we did not implement (a)?
Neha: Please correct me if I failed to see your point. In this proposed scheme,
a new segment will be rolled out depending on whichever of the size limit or
the time limit is hit first. So, if a producer produces data fast enough, it
can still create multiple segments due to the size limit on each segment. I
have set the time interval of rolling = retention time interval. In this case,
if the segments don't hit the size limit within the retention time (due to
aggressive retention time or slow production of data), then what you said will
be true and there will be at most two active segments in the log at any point
of time. In the first case, the application indeed wanted its data cleaned up
fast and in the second case, hopefully the number of segments should not
matter.
Including your other suggestions in the patch.
> Time based log segment rollout
> ------------------------------
>
> Key: KAFKA-475
> URL: https://issues.apache.org/jira/browse/KAFKA-475
> Project: Kafka
> Issue Type: New Feature
> Affects Versions: 0.7.1
> Reporter: Swapnil Ghike
> Assignee: Swapnil Ghike
> Labels: features
> Fix For: 0.7.2
>
> Attachments: kafka-475-v1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Some applications might want their data to be deleted from the Kafka servers
> earlier than the default retention time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
