Skip to content

Conversation

@stefan-egli
Copy link
Contributor

No description provided.

stefan-egli and others added 17 commits February 9, 2021 10:40
…he default of 'oak.referenceableFrozenNode' being true in 1.22 for backwards compatibility reason - while in trunk it is false to promote the new behaviour there
Merge 1.22 branch from upstream
…rence: the default of 'oak.referenceableFrozenNode' being true in 1.22 for backwards compatibility reason - while in trunk it is false to promote the new behaviour there"

This reverts commit 5ca5bde.
…enceableFrozenNode==true (in trunk it is false) - requires adjustments of a few tests
merge from upstream/1.22
… a one-time half-CPU-using repository traversal that fixes missing _bc entries that the original sweep was missing: A repository that was ever running with Oak older than 1.8 and that upgraded to a version without this OAK-9176 fix might have missing _bc entries - sweep2 will fix that. Sweep2 can be disabled if it causes problems: via a System Property -Doak.documentMK.disableSweep2=true

git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1882480 13f79535-47bb-0310-9956-ffa450edef68
@stefan-egli
Copy link
Contributor Author

Note that the commits before

OAK-9134 related : removed unused imports 

were just branch-merge-yoga and do not contain any diff (except this particular unused import)

Copy link
Contributor

@mreutegg mreutegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is usually done by the person who creates the release based on information in JIRA.
I think it would be better if additional information is added further up in the release notes.


[OAK-9261] - Upgrade Apache Solr to 8.6.3 and remove Embedded Solr Server
[OAK-9176] - Fix for sweep missing _bc (branch commit) entries in some cases - plus sweep2 introduced to clean up repository accordingly.
PS: use -Doak.documentMK.disableSweep2=true to disable sweep2 in case it should be skipped explicitly
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is usually done by the person who creates the release based on information in JIRA.
I think it would be better if additional information is added further up in the release notes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PS: There's also details in the upgrade page..

@mreutegg
Copy link
Contributor

mreutegg commented Apr 6, 2021

Compared the commit on trunk (https://github.com/apache/jackrabbit-oak/commit/db584aa52b8e8b7351d40d1fac5de1e3bad43aff.patch) with the one on this branch (https://github.com/apache/jackrabbit-oak/commit/db584aa52b8e8b7351d40d1fac5de1e3bad43aff.patch) and it looks good to me.

@stefan-egli
Copy link
Contributor Author

Thx, I'll merge the PR to svn next

@stefan-egli
Copy link
Contributor Author

Merged to svn in rev 1888445

@stefan-egli stefan-egli closed this Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants