[
https://issues.apache.org/jira/browse/KAFKA-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986199#comment-13986199
]
alexcb commented on KAFKA-1425:
-------------------------------
yup sure enough, the kafka-patch-review.py does not appear to be checking for
errors and will happily move on and upload a patch.
[vagrant@centosdev kafka_git_repo]$ python2.7 kafka-patch-review.py -b trunk -j
KAFKA-1425
Configuring reviewboard url to https://reviews.apache.org
Updating your remote branches to pull the latest changes
sh: post-review: command not found
Creating diff against trunk and uploading patch to JIRA KAFKA-1425
Created a new reviewboard
> provide logStartOffset in addition to LogEndOffset metric
> ---------------------------------------------------------
>
> Key: KAFKA-1425
> URL: https://issues.apache.org/jira/browse/KAFKA-1425
> Project: Kafka
> Issue Type: Improvement
> Reporter: alexcb
> Priority: Minor
> Attachments: KAFKA-1425.patch, KAFKA-1425.patch
>
>
> Hello,
> Would it be possible to include a metric to report the minimum message offset
> for each topic/partition? This would mirror the LogEndOffset which is already
> provided.
> There's also a Size metric that's provided; however, this gives us the size
> of a topic/partition in bytes so I'm unable to calculate the
> Starting/beginning message offset based on the end offset.
> I've attached a patch I used with kafka 0.8.1 to expose this metric.
> Thanks,
> Alex
--
This message was sent by Atlassian JIRA
(v6.2#6252)
