-
Notifications
You must be signed in to change notification settings - Fork 1
proof of concept for message durability #1
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
base: master
Are you sure you want to change the base?
Conversation
/** Flush events in the message queue. */ | ||
public void flush() { | ||
client.flush(); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Looks to be a breaking change. Could we implement the flush
method based on the new architecture? or at least depreciate it with empty or minimal implementation (warning log)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this method is misleading. Flushing does not guarantee that messages will be delivered.
IMHO the API for segment should be a simple, "hey, there is the message, do your best"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand your point. I'm just thinking about binary compatibility, the upgrade should ideally not require any changes from users.
#2 another approach using small size files |
No description provided.