Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message containing broker received timestamp #136

Closed
DongbinNie opened this issue Dec 2, 2016 · 2 comments
Closed

Message containing broker received timestamp #136

DongbinNie opened this issue Dec 2, 2016 · 2 comments
Labels
type/feature The PR added a new feature or issue requested a new feature

Comments

@DongbinNie
Copy link

Message containing broker received timestamp, it will he helpful for delayed message and resetting cursor.

[merlimat]
Why should we use the time that the broker received the message for points 2 & 4? Shouldn't be
it more appropriate to use the publisher set timestamp?

[DongbinNie]
As one Topic/Partition is served by one Broker, the timestamp received by broker will be strictly ordered. The publisher time can't be trusted as it relies on the publisher's system time and network.

@merlimat merlimat added the type/feature The PR added a new feature or issue requested a new feature label Dec 3, 2016
@merlimat merlimat changed the title [Feature Proposal] Message containing broker received timestamp Message containing broker received timestamp Dec 3, 2016
sijie pushed a commit to sijie/pulsar that referenced this issue Mar 4, 2018
* adding windowing to Pulsar functions

* cleaning up

* relocating code
@ivankelly
Copy link
Contributor

@DongbinNie broker timestamps may not be strictly ordered in the case that a topic moves between brokers. What is the use case for this?

@ivankelly
Copy link
Contributor

Closing due to lack of activity. Feel free to reopen if you want to pick it up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature The PR added a new feature or issue requested a new feature
Projects
None yet
Development

No branches or pull requests

3 participants