[jira] [Commented] (OAK-10498) Build Jackrabbit/jackrabbit-oak-trunk #1199 failed
[ https://issues.apache.org/jira/browse/OAK-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776365#comment-17776365 ] Hudson commented on OAK-10498: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1202|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1202/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1202/console] > Build Jackrabbit/jackrabbit-oak-trunk #1199 failed > -- > > Key: OAK-10498 > URL: https://issues.apache.org/jira/browse/OAK-10498 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1199 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1199|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10499) Node bundling may resurrect node
[ https://issues.apache.org/jira/browse/OAK-10499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776263#comment-17776263 ] Marcel Reutegger commented on OAK-10499: Created a draft PR with an ignored test that reproduces the issue: https://github.com/apache/jackrabbit-oak/pull/1160 > Node bundling may resurrect node > > > Key: OAK-10499 > URL: https://issues.apache.org/jira/browse/OAK-10499 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Marcel Reutegger >Priority: Major > > In some cases the DocumentNodeStore node bundling features may resurrect > nodes that have been deleted. The issue happens when the following conditions > are met: > - The repository contains a node structure with bundled nodes > - There is a non-bundled node below a bundled node > - The node structure is removed with a clusterId different from the one used > when the nodes were created > - The node structure is partially re-created with a primary type that is not > configured for node bundling and with a clusterId different from the one used > when the nodes were removed. > After this sequence the non-bundled descendant node is resurrected, even > though it was not recreated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10499) Node bundling may resurrect node
[ https://issues.apache.org/jira/browse/OAK-10499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-10499: --- Description: In some cases the DocumentNodeStore node bundling features may resurrect nodes that have been deleted. The issue happens when the following conditions are met: - The repository contains a node structure with bundled nodes - There is a non-bundled node below a bundled node - The node structure is removed with a clusterId different from the one used when the nodes were created - The node structure is partially re-created with a primary type that is not configured for node bundling and with a clusterId different from the one used when the nodes were removed. After this sequence the non-bundled descendant node is resurrected, even though it was not recreated. was: In some cases the DocumentNodeStore node bundling features may resurrect nodes that have been deleted. The issue happens when the following conditions are met: - The repository contains a node structure with bundled nodes - There is a non-bundled node below a bundled node - The node structure is removed with a clusterId different from the one used when the nodes were created - The node structure is partially re-created with a primary type that is not configured for node bundling and with a clusterId different from the one used when the nodes were removed. After this sequence the non-bundled descendant node is resurrected, even though it was not recreated. > Node bundling may resurrect node > > > Key: OAK-10499 > URL: https://issues.apache.org/jira/browse/OAK-10499 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Marcel Reutegger >Priority: Major > > In some cases the DocumentNodeStore node bundling features may resurrect > nodes that have been deleted. The issue happens when the following conditions > are met: > - The repository contains a node structure with bundled nodes > - There is a non-bundled node below a bundled node > - The node structure is removed with a clusterId different from the one used > when the nodes were created > - The node structure is partially re-created with a primary type that is not > configured for node bundling and with a clusterId different from the one used > when the nodes were removed. > After this sequence the non-bundled descendant node is resurrected, even > though it was not recreated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10499) Node bundling may resurrect node
Marcel Reutegger created OAK-10499: -- Summary: Node bundling may resurrect node Key: OAK-10499 URL: https://issues.apache.org/jira/browse/OAK-10499 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk Reporter: Marcel Reutegger In some cases the DocumentNodeStore node bundling features may resurrect nodes that have been deleted. The issue happens when the following conditions are met: - The repository contains a node structure with bundled nodes - There is a non-bundled node below a bundled node - The node structure is removed with a clusterId different from the one used when the nodes were created - The node structure is partially re-created with a primary type that is not configured for node bundling and with a clusterId different from the one used when the nodes were removed. After this sequence the non-bundled descendant node is resurrected, even though it was not recreated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10497) Properties order in FFS can be different across runs
[ https://issues.apache.org/jira/browse/OAK-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776117#comment-17776117 ] Nitin Gupta commented on OAK-10497: --- PR [https://github.com/apache/jackrabbit-oak/pull/1158] > Properties order in FFS can be different across runs > > > Key: OAK-10497 > URL: https://issues.apache.org/jira/browse/OAK-10497 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > > While building the FFS, the order of the properties can be different for the > same node across different builds/runs. > > This does not have any impact on indexing, but in case there's a need for > verification across different strategies to compare if the FFS built is the > same - this sometimes lead to false failures. > > We should ensure a sorted order of the properties of every node in the FFS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10498) Build Jackrabbit/jackrabbit-oak-trunk #1199 failed
[ https://issues.apache.org/jira/browse/OAK-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776112#comment-17776112 ] Hudson commented on OAK-10498: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1201|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1201/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1201/console] > Build Jackrabbit/jackrabbit-oak-trunk #1199 failed > -- > > Key: OAK-10498 > URL: https://issues.apache.org/jira/browse/OAK-10498 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1199 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1199|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10498) Build Jackrabbit/jackrabbit-oak-trunk #1199 failed
[ https://issues.apache.org/jira/browse/OAK-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776107#comment-17776107 ] Hudson commented on OAK-10498: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1200|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1200/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1200/console] > Build Jackrabbit/jackrabbit-oak-trunk #1199 failed > -- > > Key: OAK-10498 > URL: https://issues.apache.org/jira/browse/OAK-10498 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1199 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1199|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10493) Build Jackrabbit/jackrabbit-oak-trunk #1196 failed
[ https://issues.apache.org/jira/browse/OAK-10493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776106#comment-17776106 ] Hudson commented on OAK-10493: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1198|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1198/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1198/console] > Build Jackrabbit/jackrabbit-oak-trunk #1196 failed > -- > > Key: OAK-10493 > URL: https://issues.apache.org/jira/browse/OAK-10493 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1196 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1196|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1196/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1196/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10498) Build Jackrabbit/jackrabbit-oak-trunk #1199 failed
Hudson created OAK-10498: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1199 failed Key: OAK-10498 URL: https://issues.apache.org/jira/browse/OAK-10498 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1199 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1199|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1199/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10495) Ignore DocumentStoreIndexerIT#parallelReindex* tests
[ https://issues.apache.org/jira/browse/OAK-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-10495. - Resolution: Fixed On trunk with commit - [https://github.com/apache/jackrabbit-oak/commit/13889a17d143d7a24b2907f6626f3c03f7ed07a1] > Ignore DocumentStoreIndexerIT#parallelReindex* tests > > > Key: OAK-10495 > URL: https://issues.apache.org/jira/browse/OAK-10495 > Project: Jackrabbit Oak > Issue Type: Bug > Components: run >Reporter: Amit Jain >Assignee: Amit Jain >Priority: Major > Fix For: 1.60.0 > > > The tests are flaky and fail often: > [INFO] Running org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT > [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 80.779 s <<< FAILURE! - in > org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT > [ERROR] > parallelReindexWithLZ4(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT) > Time elapsed: 15.874 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:87) > at org.junit.Assert.assertTrue(Assert.java:42) > at org.junit.Assert.assertFalse(Assert.java:65) > at org.junit.Assert.assertFalse(Assert.java:75) > at > org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:262) > at > org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexWithLZ4(DocumentStoreIndexerIT.java:182) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10497) Properties order in FFS can be different across runs
[ https://issues.apache.org/jira/browse/OAK-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Gupta reassigned OAK-10497: - Assignee: Nitin Gupta > Properties order in FFS can be different across runs > > > Key: OAK-10497 > URL: https://issues.apache.org/jira/browse/OAK-10497 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Nitin Gupta >Assignee: Nitin Gupta >Priority: Major > > While building the FFS, the order of the properties can be different for the > same node across different builds/runs. > > This does not have any impact on indexing, but in case there's a need for > verification across different strategies to compare if the FFS built is the > same - this sometimes lead to false failures. > > We should ensure a sorted order of the properties of every node in the FFS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10497) Properties order in FFS can be different across runs
Nitin Gupta created OAK-10497: - Summary: Properties order in FFS can be different across runs Key: OAK-10497 URL: https://issues.apache.org/jira/browse/OAK-10497 Project: Jackrabbit Oak Issue Type: Task Reporter: Nitin Gupta While building the FFS, the order of the properties can be different for the same node across different builds/runs. This does not have any impact on indexing, but in case there's a need for verification across different strategies to compare if the FFS built is the same - this sometimes lead to false failures. We should ensure a sorted order of the properties of every node in the FFS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10432) DocumentStoreIndexerIT failures
[
https://issues.apache.org/jira/browse/OAK-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Kataria resolved OAK-10432.
-
Resolution: Duplicate
> DocumentStoreIndexerIT failures
> ---
>
> Key: OAK-10432
> URL: https://issues.apache.org/jira/browse/OAK-10432
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: oak-run
>Reporter: Marcel Reutegger
>Assignee: Mohit Kataria
>Priority: Major
>
> Tests related to parallel indexing in DocumentStoreIndexerIT fail frequently
> on Jenkins. Output from recent failures:
> {noformat}
> [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
> 123.584 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT
> [ERROR]
> parallelReindex(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT) Time
> elapsed: 33.292 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:265)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindex(DocumentStoreIndexerIT.java:176)
> ...
> [ERROR]
> parallelReindexWithLZ4(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT)
> Time elapsed: 29.313 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:265)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexWithLZ4(DocumentStoreIndexerIT.java:184)
> {noformat}
> See also previously reported issue OAK-10381.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10432) DocumentStoreIndexerIT failures
[
https://issues.apache.org/jira/browse/OAK-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776062#comment-17776062
]
Mohit Kataria commented on OAK-10432:
-
[~amitj] had marked these as ignored in linked issue.
Marking this as resolved.
> DocumentStoreIndexerIT failures
> ---
>
> Key: OAK-10432
> URL: https://issues.apache.org/jira/browse/OAK-10432
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: oak-run
>Reporter: Marcel Reutegger
>Assignee: Mohit Kataria
>Priority: Major
>
> Tests related to parallel indexing in DocumentStoreIndexerIT fail frequently
> on Jenkins. Output from recent failures:
> {noformat}
> [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
> 123.584 s <<< FAILURE! - in
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT
> [ERROR]
> parallelReindex(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT) Time
> elapsed: 33.292 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:265)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindex(DocumentStoreIndexerIT.java:176)
> ...
> [ERROR]
> parallelReindexWithLZ4(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT)
> Time elapsed: 29.313 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:265)
> at
> org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexWithLZ4(DocumentStoreIndexerIT.java:184)
> {noformat}
> See also previously reported issue OAK-10381.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9980) Index Purging Logic fails when trying to delete :oak:mount-libs* (read-only) node under index definition for composite nodestore
[ https://issues.apache.org/jira/browse/OAK-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohit Kataria resolved OAK-9980. Resolution: Fixed > Index Purging Logic fails when trying to delete :oak:mount-libs* (read-only) > node under index definition for composite nodestore > > > Key: OAK-9980 > URL: https://issues.apache.org/jira/browse/OAK-9980 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Mohit Kataria >Assignee: Mohit Kataria >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10496) [Tech Debt] Disable/Remove parallel indexing
Amit Jain created OAK-10496: --- Summary: [Tech Debt] Disable/Remove parallel indexing Key: OAK-10496 URL: https://issues.apache.org/jira/browse/OAK-10496 Project: Jackrabbit Oak Issue Type: Task Components: run Reporter: Amit Jain Task to remove or disable parallel indexing. The parallel indexing feature is not used and the recommendation is to use PIPELINED for indexing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10491) Indexing: pass a MongoDatabase instance instead of MongoConnection to indexing logic
[ https://issues.apache.org/jira/browse/OAK-10491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nuno Santos resolved OAK-10491. --- Fix Version/s: 1.60.0 Resolution: Done > Indexing: pass a MongoDatabase instance instead of MongoConnection to > indexing logic > > > Key: OAK-10491 > URL: https://issues.apache.org/jira/browse/OAK-10491 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Nuno Santos >Priority: Major > Fix For: 1.60.0 > > > The pipeline indexing strategy needs to have access to a MongoDatabase object > to register a custom codec to deserialize the responses from Mongo. > Previously we were passing a MongoConnection object which contained a > reference to MongoDatabase. But the indexing job does not need any other > fields from MongoConnection other than MongoDatabase. But requiring > MongoConnection makes it harder for users of Oak to call this API. > We can simplify the logic by requiring only a MongoConnection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10495) Ignore DocumentStoreIndexerIT#parallelReindex* tests
Amit Jain created OAK-10495: --- Summary: Ignore DocumentStoreIndexerIT#parallelReindex* tests Key: OAK-10495 URL: https://issues.apache.org/jira/browse/OAK-10495 Project: Jackrabbit Oak Issue Type: Bug Components: run Reporter: Amit Jain Assignee: Amit Jain Fix For: 1.60.0 The tests are flaky and fail often: [INFO] Running org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 80.779 s <<< FAILURE! - in org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT [ERROR] parallelReindexWithLZ4(org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT) Time elapsed: 15.874 s <<< FAILURE! java.lang.AssertionError at org.junit.Assert.fail(Assert.java:87) at org.junit.Assert.assertTrue(Assert.java:42) at org.junit.Assert.assertFalse(Assert.java:65) at org.junit.Assert.assertFalse(Assert.java:75) at org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexInternal(DocumentStoreIndexerIT.java:262) at org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT.parallelReindexWithLZ4(DocumentStoreIndexerIT.java:182) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10486) Resolution of inherited groups may terminate pre-maturely for external users
[ https://issues.apache.org/jira/browse/OAK-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber resolved OAK-10486. Resolution: Fixed > Resolution of inherited groups may terminate pre-maturely for external users > > > Key: OAK-10486 > URL: https://issues.apache.org/jira/browse/OAK-10486 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-external >Reporter: Angela Schreiber >Assignee: Angela Schreiber >Priority: Major > Fix For: 1.60.0 > > > for external users with dynamic membership the resolution of inherited local > groups terminates pre-maturely when multiple external groups are combined > with different local groups. > this only applies to User.memberOf calls, while principal-resolution (such as > performed during login), the associated permission evaluation and looking up > group members and membership for groups is not affected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
