[
https://issues.apache.org/jira/browse/KAFKA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977395#comment-15977395
]
Jun Rao commented on KAFKA-566:
-------------------------------
[~jozi-k], thanks for your interest. I am not sure if [~sriharsha] is still
working on this. Currently, on the server side, each LogSegment already
maintains a largestTimestamp. So, we could easily figure out the largest
timestamp in a partition. The question is how to expose this information back
to the client. Extending TopicMetadataRequest seems like a natural choice.
However, the issue is that TopicMetadataRequest can be answered from any
broker, but largestTimestamp can only be answered from the broker that hosts
the topic/partition. So, we may need a different request to get that
information.
> Add last modified time to the TopicMetadataRequest
> --------------------------------------------------
>
> Key: KAFKA-566
> URL: https://issues.apache.org/jira/browse/KAFKA-566
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Jay Kreps
> Assignee: Sriharsha Chintalapani
>
> To support KAFKA-560 it would be nice to have a last modified time in the
> TopicMetadataRequest. This would be the timestamp of the last append to the
> log as taken from stat on the final log segment.
> Implementation would involve
> 1. Adding a new field to TopicMetadataRequest
> 2. Adding a method Log.lastModified: Long to get the last modified time from
> a log
> This timestamp would, of course, be subject to error in the event that the
> file was touched without modification, but I think that is actually okay
> since it provides a manual way to avoid gc'ing a topic that you know you
> will want.
> It is debatable whether this should go in 0.8. It would be nice to add the
> field to the metadata request, at least, as that change should be easy and
> would avoid needing to bump the version in the future.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
