-
Notifications
You must be signed in to change notification settings - Fork 6
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
hotfix/dev-107.4.0 -> develop #2063
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Events have no ID or other distinct fields and multiple events may be recoreded at the same time, fetching a block must start at the time of the last event of the previous batch (inclusively). To prevent duplicates and because no fields are distinct by default, callers must provide a duplicate preventer based on the type of events they wish to fetch. Fixes: SE-14230 (cherry picked from commit eb19a72)
…only the user data is important. This will e.g. allow re-using constraints on the user data fields for different event types as well as to allow a default duplicate preventer for streaming events (in a future commit). An interface is used instead of an abstract class to keep the inheritance limitations low. Fixes: SE-14230 (cherry picked from commit 198ac89)
…ter. Fixes: SE-14230 (cherry picked from commit 612f676)
… preventer. Fixes: SE-14230 (cherry picked from commit ca6a5c8)
Fixes: SE-14230 (cherry picked from commit a75e2f5)
Fixes: SE-14230 (cherry picked from commit 6ff0eba)
Fixes: SE-14230 (cherry picked from commit e56b7d6)
…ist of events to the duplicate preventer. In case of user events, the timestamp is now only added once and not for each event. Fixes: SE-14230 (cherry picked from commit 4027414)
…ng the caller to provide distinct fields. Duplicates are then prevented by ignoring all events for the same timestamp where all fields match one of the previously fetched events. Fixes: SE-14230 (cherry picked from commit 0d9de1f)
…pe and tenant ID. While the user ID is most probably already unique to the type of event queried, that mustn't be the case for all events. Fixes: SE-14230 (cherry picked from commit d40bbbc)
Fixes: SE-14230 (cherry picked from commit 554d873)
Co-authored-by: Sascha Bieberstein <sabieber@users.noreply.github.com> Co-authored-by: Matthias Keck <60612914+mkeckmkeck@users.noreply.github.com> (cherry picked from commit 4334479)
… example. Fixes: SE-14230 (cherry picked from commit c79ad96)
Fixes: SE-14230 (cherry picked from commit 707c3b0)
…aming-Hotfix SE-14230: Cherry Picks Event Streaming for Hotfix
This PR can only be merged after at least one of our categorizing labels has been added: 💣 BREAKING CHANGE, 🧬 Enhancement, 🐛 Bugfix, 🛠️ Maintenance, ⬆️ Dependencies |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Additional Notes
Checklist