Update dependency org.agrona:agrona to v2.3.1#2986
Merged
singhpk234 merged 1 commit intoapache:mainfrom Nov 6, 2025
Merged
Conversation
singhpk234
approved these changes
Nov 6, 2025
XN137
pushed a commit
to XN137/polaris
that referenced
this pull request
Nov 6, 2025
snazy
added a commit
to snazy/polaris
that referenced
this pull request
Nov 20, 2025
* fix typo in Ozone getting-started guide (apache#2975) * NoSQL: Persistence API (apache#2965) Provides the persistence API parts for the NoSQL persistence work. Most of this PR are purely interfaces and annotations. It consists of a low-level `Persistence` interface to read and write individual `Obj`ects and the corresponding pluggable `ObjType`s. The API module also contains upstream SPIs for database specific implementations and downstream APIs for atomic commits and indexes. Also some CDI specific infrastructure helper annotations. Unit tests cover the few pieces of actual executable code in this change. This change also adds a README, which references functionality and modules that are not in this PR, but already provide an overview of the overall interactions. * Handle poetry lock update (apache#2942) * Update dependency com.azure:azure-sdk-bom to v1.3.2 (apache#2979) * Added interface for reporting metrics (apache#2887) Co-authored-by: Alexandre Dutra <[email protected]> * Prefer RealmConfig fields (apache#2971) minor cleanup of verbose code * Update community meetings note links due to document split (apache#2981) * NoSQL: database agnostic implementation + in-memory backend (apache#2977) This change contains the database agnostic implementation plus the in-memory backend used for testing purposes, and a Junit extension. These three modules are difficult to put into isolated PRs. The "main implementation" contains the commit-logic, indexes-logic and the caching part. `PersistenceImplementation` is (more or less) a wrapper providing higher-level functionality backed by a database's `Backend` implementation. The latter provides the bare minimum functionality. Other implementations of the `Persistence` interface are just to transparently add caching and commit-attempt specific case. No call site needs to bother about the actual implementation and/or its layers. Tests in the `polaris-persistence-nosql-impl` module use the in-memory backend via the Junit extension. Common tests for all backends, in-memory in this PR and MongoDB in a follow-up, are in the testFixtures of the `polaris-persistence-nosql-impl`. * Fix incorrect column name in ModelEvent (apache#2987) Fixes apache#2913 * Rename request ID header (apache#2988) * Update dependency org.agrona:agrona to v2.3.1 (apache#2986) * Update actions/stale digest to fad0de8 (apache#2984) * Last merged commit 291bd7d --------- Co-authored-by: Dmitri Bourlatchkov <[email protected]> Co-authored-by: Yong Zheng <[email protected]> Co-authored-by: Mend Renovate <[email protected]> Co-authored-by: cccs-cat001 <[email protected]> Co-authored-by: Alexandre Dutra <[email protected]> Co-authored-by: Christopher Lambert <[email protected]> Co-authored-by: JB Onofré <[email protected]>
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
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.
This PR contains the following updates:
2.2.4->2.3.1Release Notes
aeron-io/agrona (org.agrona:agrona)
v2.3.1Compare Source
org.agrona.MarkFile.mapNewOrExistingMarkFile. (#340)ByteBuddy1.17.8.Checkstyle12.1.1.JUnit6.0.1.v2.3.0Compare Source
[Breaking] Changed
org.agrona.concurrent.ShutdownSignalBarrierto use shutdown hooks instead of signals.Previously
ShutdownSignalBarrierrelied on interceptingSIGINTandSIGTERMOS signals by overriding JVM's signal handling which was preventing shutdown hooks from be executed. This in turn was breaking applications and frameworks that relied on shutdown hooks for clean termination.New implementation uses shutdown hooks instead and requires
ShutdownSignalBarrierto be explicitly closed.NB: Failure to close
ShutdownSignalBarriermight result in JVM not terminating!As the result the code using
ShutdownSignalBarrierneeds to be updated:In the above example
ShutdownSignalBarrieris closed last to ensure thatserviceterminates completely beforeShutdownSignalBarriercloses which in turn allows JVM to exit.[Breaking] Deprecated
org.agrona.concurrent.SigIntfor removal. Useorg.agrona.concurrent.ShutdownSignalBarrierinstead.NB:
org.agrona.concurrent.SigInt.register(java.lang.Runnable)is unsafe as it overridesSIGINTsignal handling of the JVM thus preventing shutdown hooks from being executed.An example using
ShutdownSignalBarrierinstead ofSigInt:[Breaking] Agrona jars no longer provide OSGI metadata as
bndplugin was removed, because it breakscompatibility with Gradle 9.1 and causes self-dependency via
baselinetask.AtomicCounter minor javadoc improvements. (#338)
Upgrade to
Gradle9.1.0.Upgrade to
ByteBuddy1.17.7.Upgrade to
Checkstyle11.1.0.Upgrade to
JUnit5.13.4.Upgrade to
Mockito5.20.0.Upgrade to
Shadow9.2.2.Upgrade to
Versions0.53.0.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.