This is an automated email from the ASF dual-hosted git repository.
jsedding pushed a change to branch jsedding/OAK-12005-re-use-uuid-instances
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git
discard 26c3dfc22a OAK-12005 - segment preloading graph-cache uses too much
heap
add 390950b33e OAK-11999: Release Oak 1.88.0 - update oak-doc* version
numbers
add ad3b3ab1d4 OAK-12003 Refactor code in AzurePersistenceManager (#2606)
add 22c03154b9 OAK-11991 Optimize the oak-segment recovery process
new b0d72311f1 OAK-12005 - segment preloading graph-cache uses too much
heap
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (26c3dfc22a)
\
N -- N -- N refs/heads/jsedding/OAK-12005-re-use-uuid-instances
(b0d72311f1)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
oak-doc-railroad-macro/pom.xml | 2 +-
oak-doc/pom.xml | 2 +-
.../oak/segment/azure/AzureArchiveManager.java | 113 +++++++++++---
.../oak/segment/azure/AzurePersistenceManager.java | 166 +++++++++++++--------
.../oak/segment/azure/AzureArchiveManagerTest.java | 29 ++++
5 files changed, 222 insertions(+), 90 deletions(-)
