[jira] [Resolved] (KAFKA-629) Generalize the getOffsets call

["Jay Kreps (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Kreps resolved KAFKA-629.
-----------------------------

    Resolution: Duplicate
    
> Generalize the getOffsets call
> ------------------------------
>
>                 Key: KAFKA-629
>                 URL: https://issues.apache.org/jira/browse/KAFKA-629
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Jay Kreps
>
> This API is a little odd. Currently it gets a list of the first offset for each segment as well as the log end offset. It lets you filter by timestamp, though this is a bit broken because it uses the timestamp of the segment file which doesn't correspond to the first offset but rather the first offset int he next segment.
> People have asked for a way to correlate time and offset. A complete mapping for this would be a bit difficult to implement (it would be a whole new persistent data structure) but a compromise would be to just replace this API with something a bit more generic.
> This would differ from the getMetadata api in that it would go to the master for a given partition, so it can give info on the Log. That API answers questions that any broker can answer.
> This could be called something like getPartitionMetadata. It would go only to the master for a given partition. It would give out data on each segment in the log, including (offset, timestamp, size_in_bytes) as well as having a separate entry for the logEndOffset.

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