[
https://issues.apache.org/jira/browse/KAFKA-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Bedford resolved KAFKA-4892.
----------------------------------
Resolution: Not A Problem
this was due to cockpit error. i thought the timestamp was based on create
time of log segment. not last-modified.. when i started using that attribute
everything started to make sense. sorry for the false alarm !
> kafka 0.8.2.1 getOffsetsBefore API returning correct offset given timestamp
> in unix epoch format
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4892
> URL: https://issues.apache.org/jira/browse/KAFKA-4892
> Project: Kafka
> Issue Type: Bug
> Components: clients, offset manager
> Affects Versions: 0.8.2.1
> Environment: ubuntu 16.04
> Reporter: Chris Bedford
>
> I am seeing unexpected behavior in the getOffsetsBefore method of the client
> API.
> I understand the granularity of 'start-from-offset' via kafka spout is based
> on how many log segments you have.
> I have created a demo program that repro's this on my
> git hub account [
> https://github.com/buildlackey/kafkaOffsetBug/blob/master/README.md ],
> and I have also posted this same question to stack overflow with
> a detailed set of steps for how to repro this issue
> (using my test program and scripts).
> See:
> http://stackoverflow.com/questions/42775128/kafka-0-8-2-1-getoffsetsbefore-api-returning-correct-offset-given-timestamp-in-u
> Thanks in advance for your help !
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
