This is an automated email from the ASF dual-hosted git repository.
jsedding pushed a change to branch
jsedding/OAK-12070-reduce-azure-segmentstore-heap-usage
in repository https://gitbox.apache.org/repos/asf/jackrabbit-oak.git
discard 15f3ba1b48 OAK-12070 - Reduce memory consumption of azure segment
stores
omit bc622d1ce8 OAK-12069 - reduce SegmentPreloader memory usage
add 4470027247 OAK-12067: Utils.alignWithExternalRevisions logs timestamps
with second resolution (#2693)
add c9209db556 OAK-12068 - segment graph UUID deduplication (OAK-12005)
can be too inefficient (#2695)
new 718058c4cc OAK-12069 - reduce SegmentPreloader memory usage
new 451d1bacc9 OAK-12070 - Reduce memory consumption of azure segment
stores
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 (15f3ba1b48)
\
N -- N -- N
refs/heads/jsedding/OAK-12070-reduce-azure-segmentstore-heap-usage (451d1bacc9)
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 2 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:
.../jackrabbit/oak/segment/file/tar/TarFiles.java | 30 ++++++++--------------
.../oak/plugins/document/util/Utils.java | 7 +++--
2 files changed, 16 insertions(+), 21 deletions(-)
