Skip to content

Conversation

@yunjing
Copy link
Contributor

@yunjing yunjing commented Oct 25, 2016

Currently timestamp extraction fails for compressed messages. It would report -1 instead of the actual timestamp because the timestamps for compressed messages are stored at the block level. This PR passes down the header for the block to each of the uncompressed messages.

@yunjing
Copy link
Contributor Author

yunjing commented Oct 28, 2016

@edenhill any suggestion on this? We are trying to open source a project in a week, but this bug is blocking us.

@edenhill
Copy link
Contributor

Hey, I'll look at this during the weekend and get back to you.

@yunjing
Copy link
Contributor Author

yunjing commented Oct 28, 2016

Thanks @edenhill. Really appreciated!

@qix
Copy link

qix commented Nov 8, 2016

Hi, we've just pushed an open source project for which we require these changes in order to run in production: https://github.com/smyte/kafka_store

For now we're recommending that users install our fork, which we'll revert as soon as this makes it into a release.

edenhill added a commit that referenced this pull request Nov 16, 2016
…858, #707, #908, #345)

 - adds support for specifying the message timestamp at produce time (#707)
 - adds support for specifying topic by name rather than topic_t object (#908)
@edenhill
Copy link
Contributor

Thanks!

@edenhill edenhill closed this Nov 16, 2016
@edenhill
Copy link
Contributor

Can you verify the fix on your end, thanks?

@yunjing
Copy link
Contributor Author

yunjing commented Nov 18, 2016

Verified that it worked by compiling kafkacat with librdkafka master and consuming from several topics in production.

We have not yet incorporated the latest librdkafka in our production services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants