fix: jdbc repository return latest event with all their properties #13857
+436
−362
Conversation
This file contains hidden or 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
APIM UI Tests
|
||||||||||||||||||||||||||||
| Project |
APIM UI Tests
|
| Branch Review |
apim11726-run-e2e
|
| Run status |
|
| Run duration | 07m 02s |
| Commit |
|
| Committer | Julien Giovaresco |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
8
|
Skipped
|
0
|
Passing
|
82
|
| View all changes introduced in this branch ↗︎ | |
jgiovaresco
force-pushed
the
apim11726-run-e2e
branch
from
ccf82fa to
98a589d
Compare
ThibaudAV
approved these changes
Oct 29, 2025
...ory-jdbc/src/main/java/io/gravitee/repository/jdbc/management/JdbcEventLatestRepository.java
Show resolved
Hide resolved
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.
Issue
https://gravitee.atlassian.net/browse/APIM-11726
Description
JDBC repository that fetches the latest events, where we are building an Event without all its properties. Therefore, when the API was synchronized on the Gateway, the revision was not defined, and when an update was deployed, it was ignored because the revision number was the same.
The fix was not straightforward and may not be efficient. If we notice performance issues during the sync, we may need to investigate more on how we can improve this
JdbcEventLatestRepositoryAdditional context