You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (Created) (JIRA)" <ji...@apache.org> on 2012/01/24 20:32:40 UTC

[jira] [Created] (KAFKA-252) Investigate and change getOffsetsBefore API to a new, more general API getReplicaMetadata

Investigate and change getOffsetsBefore API to a new, more general API getReplicaMetadata
-----------------------------------------------------------------------------------------

                 Key: KAFKA-252
                 URL: https://issues.apache.org/jira/browse/KAFKA-252
             Project: Kafka
          Issue Type: Improvement
          Components: core
    Affects Versions: 0.8
            Reporter: Neha Narkhede


The relevant discussion is here - https://issues.apache.org/jira/browse/KAFKA-238?focusedCommentId=13191350&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13191350

With replication, the log segment metadata can only be returned by a broker that hosts that partition locally. It will be good to expose log segment metadata through a more general replica metadata API that in addition to returning offsets, also returns other metadata like - number of log segments, total size, last modified timestamp etc

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

        

[jira] [Updated] (KAFKA-252) Investigate and change getOffsetsBefore API to a new, more general API getReplicaMetadata

Posted by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KAFKA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede updated KAFKA-252:
--------------------------------

    Priority: Critical  (was: Major)

Since we are breaking wire protocol and APIs in 0.8, it is important to think about this as part of 0.8
                
> Investigate and change getOffsetsBefore API to a new, more general API getReplicaMetadata
> -----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-252
>                 URL: https://issues.apache.org/jira/browse/KAFKA-252
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Priority: Critical
>              Labels: replication
>
> The relevant discussion is here - https://issues.apache.org/jira/browse/KAFKA-238?focusedCommentId=13191350&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13191350
> With replication, the log segment metadata can only be returned by a broker that hosts that partition locally. It will be good to expose log segment metadata through a more general replica metadata API that in addition to returning offsets, also returns other metadata like - number of log segments, total size, last modified timestamp etc

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