Skip to content

Conversation

@apuig
Copy link

@apuig apuig commented Mar 26, 2025

No description provided.

@jeromepochat jeromepochat changed the title proof of concept for message durability [BEE-56556] proof of concept for message durability Mar 27, 2025
@jeromepochat jeromepochat changed the title [BEE-56556] proof of concept for message durability proof of concept for message durability Mar 27, 2025
Comment on lines -93 to -97
/** Flush events in the message queue. */
public void flush() {
client.flush();
}

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)?

Copy link
Author

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"

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.

@apuig
Copy link
Author

apuig commented Apr 10, 2025

#2 another approach using small size files

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.

2 participants