[jira] [Assigned] (OAK-10478) Update Mockito dependency to 5.x
[ https://issues.apache.org/jira/browse/OAK-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke reassigned OAK-10478: Assignee: Manfred Baedke (was: Julian Reschke) > Update Mockito dependency to 5.x > > > Key: OAK-10478 > URL: https://issues.apache.org/jira/browse/OAK-10478 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780297#comment-17780297
]
Manfred Baedke commented on OAK-9459:
-
New PR#1183 including [~reschke] 's suggested changes.
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780299#comment-17780299
]
Manfred Baedke commented on OAK-9459:
-
trunk:
[9014aff8|https://github.com/apache/jackrabbit-oak/commit/9014aff808075807f2c742cd1751b090b1ac049c]
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Baedke updated OAK-9459:
Fix Version/s: 1.60.0
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
> Fix For: 1.60.0
>
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Baedke resolved OAK-9459.
-
Resolution: Fixed
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
> Fix For: 1.60.0
>
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780299#comment-17780299
]
Manfred Baedke edited comment on OAK-9459 at 10/27/23 10:17 AM:
trunk (1.60.0):
[9014aff8|https://github.com/apache/jackrabbit-oak/commit/9014aff808075807f2c742cd1751b090b1ac049c]
was (Author: baedke):
trunk:
[9014aff8|https://github.com/apache/jackrabbit-oak/commit/9014aff808075807f2c742cd1751b090b1ac049c]
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
> Fix For: 1.60.0
>
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[ https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reopened OAK-10460: -- > PIPELINED strategy fails with OOME during final merge phase for very large > repositories > --- > > Key: OAK-10460 > URL: https://issues.apache.org/jira/browse/OAK-10460 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Nuno Santos >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[
https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780303#comment-17780303
]
Julian Reschke commented on OAK-10460:
--
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
> PIPELINED strategy fails with OOME during final merge phase for very large
> repositories
> ---
>
> Key: OAK-10460
> URL: https://issues.apache.org/jira/browse/OAK-10460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.60.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[
https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780303#comment-17780303
]
Julian Reschke edited comment on OAK-10460 at 10/27/23 10:49 AM:
-
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
That's because the URL returned for the test file is
{{file:/C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}},
so {{url.getPath()}} returns
{{C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}}.
was (Author: reschke):
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
That's because the URL returned for the test file is
{{file:/C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}},
so {{url.getPath()}} returns
{{C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}}
> PIPELINED strategy fails with OOME during final merge phase for very large
> repositories
> ---
>
> Key: OAK-10460
> URL: https://issues.apache.org/jira/browse/OAK-10460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.60.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[
https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780303#comment-17780303
]
Julian Reschke edited comment on OAK-10460 at 10/27/23 10:49 AM:
-
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
That's because the URL returned for the test file is
{{file:/C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}},
so {{url.getPath()}} returns
{{C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}}
was (Author: reschke):
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
> PIPELINED strategy fails with OOME during final merge phase for very large
> repositories
> ---
>
> Key: OAK-10460
> URL: https://issues.apache.org/jira/browse/OAK-10460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.60.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[ https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10460. -- Resolution: Fixed > PIPELINED strategy fails with OOME during final merge phase for very large > repositories > --- > > Key: OAK-10460 > URL: https://issues.apache.org/jira/browse/OAK-10460 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Nuno Santos >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[
https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780303#comment-17780303
]
Julian Reschke edited comment on OAK-10460 at 10/27/23 11:01 AM:
-
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
That's because the URL returned for the test file is
{{file:/C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}},
so {{url.getPath()}} returns
{{C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}}.
(fixed in additional commit)
was (Author: reschke):
The tests currently fail on Windows:
{noformat}
[ERROR] Errors:
[ERROR] PipelinedMergeSortTaskTest.oneFileToMerge:54->getTestFile:82 »
InvalidPath Ill...
[ERROR] PipelinedMergeSortTaskTest.twoFilesToMerge:62->getTestFile:82 »
InvalidPath Il...
[INFO]
[ERROR] Tests run: 115, Failures: 0, Errors: 2, Skipped: 0
{noformat}
That's because the URL returned for the test file is
{{file:/C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}},
so {{url.getPath()}} returns
{{C:/projects/apache/oak/trunk/oak-run-commons/target/test-classes/pipelined/merge-stage-1.json}}.
> PIPELINED strategy fails with OOME during final merge phase for very large
> repositories
> ---
>
> Key: OAK-10460
> URL: https://issues.apache.org/jira/browse/OAK-10460
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.60.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10460) PIPELINED strategy fails with OOME during final merge phase for very large repositories
[ https://issues.apache.org/jira/browse/OAK-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780308#comment-17780308 ] Julian Reschke commented on OAK-10460: -- trunk: [134b5af793|https://github.com/apache/jackrabbit-oak/commit/134b5af7932a941c4d17b1914c4c2014b5a9c8a0] [546e889da6|https://github.com/apache/jackrabbit-oak/commit/546e889da6782d8b67f5c9427bdfd3e496e66f7f] > PIPELINED strategy fails with OOME during final merge phase for very large > repositories > --- > > Key: OAK-10460 > URL: https://issues.apache.org/jira/browse/OAK-10460 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Nuno Santos >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9459) ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node
[
https://issues.apache.org/jira/browse/OAK-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-9459:
Labels: candidate_oak_1_22 (was: )
> ConstraintViolationException in VersionManagerImplRestore when target node
> has a property definition unknown by the frozen node
> ---
>
> Key: OAK-9459
> URL: https://issues.apache.org/jira/browse/OAK-9459
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Julian Reschke
>Assignee: Manfred Baedke
>Priority: Major
> Labels: candidate_oak_1_22
> Fix For: 1.60.0
>
>
> See https://issues.apache.org/jira/browse/JCR-4680
> {noformat}
> [ERROR] Tests run: 473, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 12.546 s <<< FAILURE! - in org.apache.jackrabbit.oak.jcr.tck.VersionIT
> [ERROR]
> testRestoreRemovesMixin(org.apache.jackrabbit.test.api.version.RestoreTest)
> Time elapsed: 0.087 s <<< ERROR!
> javax.jcr.RepositoryException:
> org.apache.jackrabbit.oak.api.CommitFailedException: OakVersion:
> Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakVersion: Unexpected RepositoryException
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> Caused by: javax.jcr.nodetype.ConstraintViolationException: No matching
> property definition found for jcr:title
> at
> org.apache.jackrabbit.test.api.version.RestoreTest.testRestoreRemovesMixin(RestoreTest.java:1486)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-9705) Explain Query tool doesn't show the correct ES query when suggest queries are made
[
https://issues.apache.org/jira/browse/OAK-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Fortino resolved OAK-9705.
---
Fix Version/s: 1.60.0
Resolution: Fixed
> Explain Query tool doesn't show the correct ES query when suggest queries are
> made
> --
>
> Key: OAK-9705
> URL: https://issues.apache.org/jira/browse/OAK-9705
> Project: Jackrabbit Oak
> Issue Type: Bug
>Reporter: Jun Zhang
>Assignee: Fabrizio Fortino
>Priority: Major
> Fix For: 1.60.0
>
>
> When running the following suggest query from AEM(ES index is available)
> {code}
> SELECT [rep:suggest()] FROM [dam:Asset] as s WHERE SUGGEST('jav')
> option(index name [damAssetElastic-7-custom-2])
> {code}
> the detailed plan show that the following query is run on ES side:
> {code}
> {"bool":\{"must":[{"query_string":{"query":"suggest?term=jav","fields":[],"type":"best_fields","default_operator":"or","max_determinized_states":1,"enable_position_increments":true,"fuzziness":"AUTO","fuzzy_prefix_length":0,"fuzzy_max_expansions":50,"phrase_slop":0,"escape":false,"auto_generate_synonyms_phrase_query":true,"fuzzy_transpositions":true,"boost":1.0}}],"adjust_pure_negative":true,"boost":1.0}}
> {code}
> Instead, the following query is actually run on ES side:
> {code}
> POST cm-p11553-e21096-publish._damassetelastic-7-custom-2/_search
> {
> "query": {
> "bool": {
> "must": [
> {
> "nested": {
> "path": ":suggest",
> "query": {
> "match_phrase_prefix": {
> ":suggest.value": {
> "query": "jav"
> }
> }
> }
> }
> }
> ],
> "adjust_pure_negative": true,
> "boost": 1
> }
> }
> }
> {code}
> the Explain query should reflect the correct ES query as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-9705) Explain Query tool doesn't show the correct ES query when suggest queries are made
[
https://issues.apache.org/jira/browse/OAK-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-9705:
Component/s: search
search-elastic
> Explain Query tool doesn't show the correct ES query when suggest queries are
> made
> --
>
> Key: OAK-9705
> URL: https://issues.apache.org/jira/browse/OAK-9705
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: search, search-elastic
>Reporter: Jun Zhang
>Assignee: Fabrizio Fortino
>Priority: Major
> Fix For: 1.60.0
>
>
> When running the following suggest query from AEM(ES index is available)
> {code}
> SELECT [rep:suggest()] FROM [dam:Asset] as s WHERE SUGGEST('jav')
> option(index name [damAssetElastic-7-custom-2])
> {code}
> the detailed plan show that the following query is run on ES side:
> {code}
> {"bool":\{"must":[{"query_string":{"query":"suggest?term=jav","fields":[],"type":"best_fields","default_operator":"or","max_determinized_states":1,"enable_position_increments":true,"fuzziness":"AUTO","fuzzy_prefix_length":0,"fuzzy_max_expansions":50,"phrase_slop":0,"escape":false,"auto_generate_synonyms_phrase_query":true,"fuzzy_transpositions":true,"boost":1.0}}],"adjust_pure_negative":true,"boost":1.0}}
> {code}
> Instead, the following query is actually run on ES side:
> {code}
> POST cm-p11553-e21096-publish._damassetelastic-7-custom-2/_search
> {
> "query": {
> "bool": {
> "must": [
> {
> "nested": {
> "path": ":suggest",
> "query": {
> "match_phrase_prefix": {
> ":suggest.value": {
> "query": "jav"
> }
> }
> }
> }
> }
> ],
> "adjust_pure_negative": true,
> "boost": 1
> }
> }
> }
> {code}
> the Explain query should reflect the correct ES query as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-9705) Explain Query tool doesn't show the correct ES query when suggest queries are made
[
https://issues.apache.org/jira/browse/OAK-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780312#comment-17780312
]
Julian Reschke commented on OAK-9705:
-
trunk:
[7b650db0aa|https://github.com/apache/jackrabbit-oak/commit/7b650db0aa25c259e31294653e9e8c4fa80cc2d4]
> Explain Query tool doesn't show the correct ES query when suggest queries are
> made
> --
>
> Key: OAK-9705
> URL: https://issues.apache.org/jira/browse/OAK-9705
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: search, search-elastic
>Reporter: Jun Zhang
>Assignee: Fabrizio Fortino
>Priority: Major
> Fix For: 1.60.0
>
>
> When running the following suggest query from AEM(ES index is available)
> {code}
> SELECT [rep:suggest()] FROM [dam:Asset] as s WHERE SUGGEST('jav')
> option(index name [damAssetElastic-7-custom-2])
> {code}
> the detailed plan show that the following query is run on ES side:
> {code}
> {"bool":\{"must":[{"query_string":{"query":"suggest?term=jav","fields":[],"type":"best_fields","default_operator":"or","max_determinized_states":1,"enable_position_increments":true,"fuzziness":"AUTO","fuzzy_prefix_length":0,"fuzzy_max_expansions":50,"phrase_slop":0,"escape":false,"auto_generate_synonyms_phrase_query":true,"fuzzy_transpositions":true,"boost":1.0}}],"adjust_pure_negative":true,"boost":1.0}}
> {code}
> Instead, the following query is actually run on ES side:
> {code}
> POST cm-p11553-e21096-publish._damassetelastic-7-custom-2/_search
> {
> "query": {
> "bool": {
> "must": [
> {
> "nested": {
> "path": ":suggest",
> "query": {
> "match_phrase_prefix": {
> ":suggest.value": {
> "query": "jav"
> }
> }
> }
> }
> }
> ],
> "adjust_pure_negative": true,
> "boost": 1
> }
> }
> }
> {code}
> the Explain query should reflect the correct ES query as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10518) IndexInfo should have a isActive() method
[ https://issues.apache.org/jira/browse/OAK-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780314#comment-17780314 ] Julian Reschke commented on OAK-10518: -- trunk: [a4ca2a5b7a|https://github.com/apache/jackrabbit-oak/commit/a4ca2a5b7a719b25044fa9dc479df8e5a6ad40c6] > IndexInfo should have a isActive() method > - > > Key: OAK-10518 > URL: https://issues.apache.org/jira/browse/OAK-10518 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Thomas Mueller >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.60.0 > > > With the composite node store, it is a bit hard to find out if an index is > active or not, as only the latest version of an index is usually active that > is mounted. Unless if there is a merges property that resolves. > The IndexInfoService / IndexInfo class should have a method isActive() so > it's easy to find out. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10504) Add indexing job total duration log message
[ https://issues.apache.org/jira/browse/OAK-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780315#comment-17780315 ] Julian Reschke commented on OAK-10504: -- trunk: [380467dbfe|https://github.com/apache/jackrabbit-oak/commit/380467dbfe681b2c10f0c98c224c100fac368d97] > Add indexing job total duration log message > --- > > Key: OAK-10504 > URL: https://issues.apache.org/jira/browse/OAK-10504 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10514) Utility method to remove unmerged branch changes
[ https://issues.apache.org/jira/browse/OAK-10514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780318#comment-17780318 ] Julian Reschke commented on OAK-10514: -- trunk: [b0ec30536f|https://github.com/apache/jackrabbit-oak/commit/b0ec30536f7466c24b6d4e98364cef0b671a0491] > Utility method to remove unmerged branch changes > > > Key: OAK-10514 > URL: https://issues.apache.org/jira/browse/OAK-10514 > Project: Jackrabbit Oak > Issue Type: Task > Components: run >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.60.0 > > > Work on detailed revision garbage collection is still in progress. Until this > is finished a utility method in oak-mongo.js would be useful to remove > unmerged branch changes on a document. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10505) Make PIPELINED the default download strategy in the indexing job
[ https://issues.apache.org/jira/browse/OAK-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780319#comment-17780319 ] Julian Reschke commented on OAK-10505: -- trunk: [d9ab316b2b|https://github.com/apache/jackrabbit-oak/commit/d9ab316b2bca5650b4eb5f50a00ef88c09694f16] > Make PIPELINED the default download strategy in the indexing job > > > Key: OAK-10505 > URL: https://issues.apache.org/jira/browse/OAK-10505 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10503) Incorrect operand in incremental FFS can lead to failure during merge step
[
https://issues.apache.org/jira/browse/OAK-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780321#comment-17780321
]
Julian Reschke commented on OAK-10503:
--
trunk:
[e904e45942|https://github.com/apache/jackrabbit-oak/commit/e904e4594274f28fd7499ec1620648893b43d6b0]
> Incorrect operand in incremental FFS can lead to failure during merge step
> --
>
> Key: OAK-10503
> URL: https://issues.apache.org/jira/browse/OAK-10503
> Project: Jackrabbit Oak
> Issue Type: Task
>Reporter: Nitin Gupta
>Assignee: Nitin Gupta
>Priority: Major
> Fix For: 1.60.0
>
>
> There could be a case where a node was moved/renamed which apparently results
> the incremental FFS to have 2 entries.
>
> For example,
> NodeA | \{"prop":"value"}
> renamed to NodeB | \{"prop":"value"}
>
> then the incremental FFS has entries -
> NodeA | \{"prop":"value"} | D
> NodeB | \{"prop":"value"} | M
>
> The second entry's operand should be A and not M.
> The above analysis is an assumption from some observations during some tests
> on a large repository.
> A more detailed test case needs to be written to investigate this further.
>
> But the impact of this is that merge for this inc store fails here
> [https://jira.corp.adobe.com/browse/GRANITE-48075#:~:text=https%3A//github.com/apache/jackrabbit%2Doak/blob/trunk/oak%2Drun%2Dcommons/src/main/java/org/apache/jackrabbit/oak/index/indexer/document/incrementalstore/MergeIncrementalFlatFileStore.java%23L118]
> .
>
> A simple solution could be to treat modification same as addition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-10503) Incorrect operand in incremental FFS can lead to failure during merge step
[
https://issues.apache.org/jira/browse/OAK-10503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10503:
-
Component/s: oak-run
> Incorrect operand in incremental FFS can lead to failure during merge step
> --
>
> Key: OAK-10503
> URL: https://issues.apache.org/jira/browse/OAK-10503
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: oak-run
>Reporter: Nitin Gupta
>Assignee: Nitin Gupta
>Priority: Major
> Fix For: 1.60.0
>
>
> There could be a case where a node was moved/renamed which apparently results
> the incremental FFS to have 2 entries.
>
> For example,
> NodeA | \{"prop":"value"}
> renamed to NodeB | \{"prop":"value"}
>
> then the incremental FFS has entries -
> NodeA | \{"prop":"value"} | D
> NodeB | \{"prop":"value"} | M
>
> The second entry's operand should be A and not M.
> The above analysis is an assumption from some observations during some tests
> on a large repository.
> A more detailed test case needs to be written to investigate this further.
>
> But the impact of this is that merge for this inc store fails here
> [https://jira.corp.adobe.com/browse/GRANITE-48075#:~:text=https%3A//github.com/apache/jackrabbit%2Doak/blob/trunk/oak%2Drun%2Dcommons/src/main/java/org/apache/jackrabbit/oak/index/indexer/document/incrementalstore/MergeIncrementalFlatFileStore.java%23L118]
> .
>
> A simple solution could be to treat modification same as addition.
--
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&focusedCommentId=17780322#comment-17780322 ] Julian Reschke commented on OAK-10497: -- trunk: [c255d16fed|https://github.com/apache/jackrabbit-oak/commit/c255d16fedc9ae718b1afd234804bd24764acf48] [63aef2f4a1|https://github.com/apache/jackrabbit-oak/commit/63aef2f4a1630f411b5dc5acc8fbb3ef96561135] > 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: Thomas Mueller >Priority: Major > Fix For: 1.60.0 > > > 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] [Updated] (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 ] Julian Reschke updated OAK-10497: - Component/s: oak-run > 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 > Components: oak-run >Reporter: Nitin Gupta >Assignee: Thomas Mueller >Priority: Major > Fix For: 1.60.0 > > > 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] [Updated] (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 ] Julian Reschke updated OAK-10497: - Fix Version/s: 1.60.0 > 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: Thomas Mueller >Priority: Major > Fix For: 1.60.0 > > > 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-10487) oak-search-elastic should perform a count request for fastQuerySize
[ https://issues.apache.org/jira/browse/OAK-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780323#comment-17780323 ] Julian Reschke commented on OAK-10487: -- trunk: [31a3341ac3|https://github.com/apache/jackrabbit-oak/commit/31a3341ac3cb6081a98e990b8323f5522c88c303] > oak-search-elastic should perform a count request for fastQuerySize > --- > > Key: OAK-10487 > URL: https://issues.apache.org/jira/browse/OAK-10487 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10495) Ignore DocumentStoreIndexerIT#parallelReindex* tests
[
https://issues.apache.org/jira/browse/OAK-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10495:
-
Description:
The tests are flaky and fail often:
{noformat}
[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)
{noformat}
was:
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)
> 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:
> {noformat}
> [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)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10495) Ignore DocumentStoreIndexerIT#parallelReindex* tests
[
https://issues.apache.org/jira/browse/OAK-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780324#comment-17780324
]
Julian Reschke commented on OAK-10495:
--
[~amitj] - is there a ticket that is still open and requests the test to be
fixed???
> 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:
> {noformat}
> [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)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10471) Implement ConflictHandler for UserPrincipalProvider Cache
[ https://issues.apache.org/jira/browse/OAK-10471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780325#comment-17780325 ] Julian Reschke commented on OAK-10471: -- trunk: [9c1fd98d68|https://github.com/apache/jackrabbit-oak/commit/9c1fd98d689dd798b5b7063eb46b4df54f0830d7] [62a3f776cb|https://github.com/apache/jackrabbit-oak/commit/62a3f776cb4febe17003f8d550c749846d561324] > Implement ConflictHandler for UserPrincipalProvider Cache > - > > Key: OAK-10471 > URL: https://issues.apache.org/jira/browse/OAK-10471 > Project: Jackrabbit Oak > Issue Type: Bug >Reporter: Nicola Scendoni >Assignee: Nicola Scendoni >Priority: Major > Fix For: 1.60.0 > > > UserPrincipalProvider can be configured to periodically cache group > membership by writing group principals on a rep:cache node. Conflict can > happens on rep:cache when cache expire and load is high. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17780328#comment-17780328 ] Julian Reschke commented on OAK-10491: -- trunk: [d7816c62b9|https://github.com/apache/jackrabbit-oak/commit/d7816c62b95a6625c2d3b5ed55f97a699cb2b2a7] > 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] [Commented] (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:comment-tabpanel&focusedCommentId=17780329#comment-17780329 ] Julian Reschke commented on OAK-10486: -- trunk: [da19433ebe|https://github.com/apache/jackrabbit-oak/commit/da19433ebe9eed5dc78e938d05fb01ce7364d3a6] > 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)
[jira] [Commented] (OAK-10490) Suggest queries return duplicate entries if prefetch is enabled
[
https://issues.apache.org/jira/browse/OAK-10490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780330#comment-17780330
]
Julian Reschke commented on OAK-10490:
--
trunk:
[763031951c|https://github.com/apache/jackrabbit-oak/commit/763031951c3962aae875ec315d961ab14798dc56]
> Suggest queries return duplicate entries if prefetch is enabled
> ---
>
> Key: OAK-10490
> URL: https://issues.apache.org/jira/browse/OAK-10490
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
> Fix For: 1.60.0
>
>
> If prefetch is enabled, and prefetch count is larger than 0, then suggest
> queries return duplicate results.
> This seems to be caused by oak-search FulltextIndex.FulltextPathCursor:
> FulltextPathCursor.next() returns a new IndexRow that references currentRow.
> But pathIterator.next() updates currentRow. So that the following code can
> return different results:
> {noformat}
> // here, excerpt1 and except2 are different:
> IndexRow row1 = fulltextPathCursor.next();
> String excerpt1 = row1.getValue("rep:excerpt"));
> IndexRow row2 = fulltextPathCursor.next();
> String excerpt2 = row2.getValue("rep:excerpt"));
> // here, excerpt1 is equal to except2:
> IndexRow row1 = fulltextPathCursor.next();
> IndexRow row2 = fulltextPathCursor.next();
> String excerpt1 = row1.getValue("rep:excerpt"));
> String excerpt2 = row2.getValue("rep:excerpt"));
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10521) Update Easymock dependency to 5.2
Manfred Baedke created OAK-10521: Summary: Update Easymock dependency to 5.2 Key: OAK-10521 URL: https://issues.apache.org/jira/browse/OAK-10521 Project: Jackrabbit Oak Issue Type: Technical task Reporter: Manfred Baedke Assignee: Manfred Baedke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10521) Update Easymock dependency to 5.2
[ https://issues.apache.org/jira/browse/OAK-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10521: - Component/s: parent > Update Easymock dependency to 5.2 > - > > Key: OAK-10521 > URL: https://issues.apache.org/jira/browse/OAK-10521 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10521) Update Easymock dependency to 5.2
[ https://issues.apache.org/jira/browse/OAK-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10521: - Description: Though Easymock 3 is currently working for us, it's known to be not fully functional with Java >=17. > Update Easymock dependency to 5.2 > - > > Key: OAK-10521 > URL: https://issues.apache.org/jira/browse/OAK-10521 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Minor > > Though Easymock 3 is currently working for us, it's known to be not fully > functional with Java >=17. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10478) Update Mockito dependency to 5.x
[ https://issues.apache.org/jira/browse/OAK-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780341#comment-17780341 ] Manfred Baedke edited comment on OAK-10478 at 10/27/23 12:19 PM: - trunk (1.60.0): [f12b4159|https://github.com/apache/jackrabbit-oak/commit/f12b4159838af7f50845b6c6492d0d895f16ba3b] was (Author: baedke): trunk: [f12b4159|https://github.com/apache/jackrabbit-oak/commit/f12b4159838af7f50845b6c6492d0d895f16ba3b] > Update Mockito dependency to 5.x > > > Key: OAK-10478 > URL: https://issues.apache.org/jira/browse/OAK-10478 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10478) Update Mockito dependency to 5.x
[ https://issues.apache.org/jira/browse/OAK-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke resolved OAK-10478. -- Resolution: Done > Update Mockito dependency to 5.x > > > Key: OAK-10478 > URL: https://issues.apache.org/jira/browse/OAK-10478 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10478) Update Mockito dependency to 5.x
[ https://issues.apache.org/jira/browse/OAK-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10478: - Fix Version/s: 1.60.0 > Update Mockito dependency to 5.x > > > Key: OAK-10478 > URL: https://issues.apache.org/jira/browse/OAK-10478 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10478) Update Mockito dependency to 5.x
[ https://issues.apache.org/jira/browse/OAK-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780341#comment-17780341 ] Manfred Baedke commented on OAK-10478: -- trunk: [f12b4159|https://github.com/apache/jackrabbit-oak/commit/f12b4159838af7f50845b6c6492d0d895f16ba3b] > Update Mockito dependency to 5.x > > > Key: OAK-10478 > URL: https://issues.apache.org/jira/browse/OAK-10478 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10522) o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21
Manfred Baedke created OAK-10522: Summary: o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21 Key: OAK-10522 URL: https://issues.apache.org/jira/browse/OAK-10522 Project: Jackrabbit Oak Issue Type: Sub-task Components: run Reporter: Manfred Baedke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10522) o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21
[
https://issues.apache.org/jira/browse/OAK-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Baedke updated OAK-10522:
-
Description:
{code:java}
[INFO] Running org.apache.jackrabbit.oak.index.ReindexIT
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.305 s
<<< FAILURE! - in org.apache.jackrabbit.oak.index.ReindexIT
[ERROR]
reindexIgnoreMissingTikaDepThrow(org.apache.jackrabbit.oak.index.ReindexIT)
Time elapsed: 0.246 s <<< ERROR!
java.lang.UnsupportedOperationException: The Security Manager is deprecated and
will be removed in a future release
at java.base/java.lang.System.setSecurityManager(System.java:429)
at
org.apache.jackrabbit.oak.index.ReindexIT.assertExits(ReindexIT.java:429)
at
org.apache.jackrabbit.oak.index.ReindexIT.reindexIgnoreMissingTikaDepThrow(ReindexIT.java:144)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418){code}
> o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21
> --
>
> Key: OAK-10522
> URL: https://issues.apache.org/jira/browse/OAK-10522
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: run
>Reporter: Manfred Baedke
>Priority: Minor
>
> {code:java}
> [INFO] Running org.apache.jackrabbit.oak.index.ReindexIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.305
> s <<< FAILURE! - in org.apache.jackrabbit.oak.index.ReindexIT
> [ERROR]
> reindexIgnoreMissingTikaDepThrow(org.apache.jackrabbit.oak.index.ReindexIT)
> Time elapsed: 0.246 s <<< ERROR!
> java.lang.UnsupportedOperationException: The Security Manager is deprecated
> and will be removed in a future release
> at java.base/java.lang.System.setSecurityManager(System.java:429)
> at
> org.apache.jackrabbit.oak.index.ReindexIT.assertExits(ReindexIT.java:429)
> at
> org.apache.jackrabbit.oak.index.ReindexIT.reindexIgnoreMissingTikaDepThrow(ReindexIT.java:144)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runner
[jira] [Commented] (OAK-10509) Build Jackrabbit/jackrabbit-oak-trunk #1228 failed
[ https://issues.apache.org/jira/browse/OAK-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780355#comment-17780355 ] Hudson commented on OAK-10509: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1245|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1245/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1245/console] > Build Jackrabbit/jackrabbit-oak-trunk #1228 failed > -- > > Key: OAK-10509 > URL: https://issues.apache.org/jira/browse/OAK-10509 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1228 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1228|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10523) Basic SNS support returns invalid node names
Julian Reschke created OAK-10523:
Summary: Basic SNS support returns invalid node names
Key: OAK-10523
URL: https://issues.apache.org/jira/browse/OAK-10523
Project: Jackrabbit Oak
Issue Type: Bug
Components: jcr
Reporter: Julian Reschke
When encountering names using index notation in storage, oak-jcr treats the
index suffix as part of the name. This causes issues with other components that
assume that the result of {{Node.getName()}} is indeed a valid JCR name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10524) SameNameSiblingTest: add (failing) test for getName() semantics
Julian Reschke created OAK-10524: Summary: SameNameSiblingTest: add (failing) test for getName() semantics Key: OAK-10524 URL: https://issues.apache.org/jira/browse/OAK-10524 Project: Jackrabbit Oak Issue Type: Technical task Components: jcr Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10522) o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21
[
https://issues.apache.org/jira/browse/OAK-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780361#comment-17780361
]
Manfred Baedke commented on OAK-10522:
--
The test case uses a custom SecurityManager to verify the exit code. Since the
SecurityManager has been removed without replacement.
> o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21
> --
>
> Key: OAK-10522
> URL: https://issues.apache.org/jira/browse/OAK-10522
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: run
>Reporter: Manfred Baedke
>Priority: Minor
>
> {code:java}
> [INFO] Running org.apache.jackrabbit.oak.index.ReindexIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.305
> s <<< FAILURE! - in org.apache.jackrabbit.oak.index.ReindexIT
> [ERROR]
> reindexIgnoreMissingTikaDepThrow(org.apache.jackrabbit.oak.index.ReindexIT)
> Time elapsed: 0.246 s <<< ERROR!
> java.lang.UnsupportedOperationException: The Security Manager is deprecated
> and will be removed in a future release
> at java.base/java.lang.System.setSecurityManager(System.java:429)
> at
> org.apache.jackrabbit.oak.index.ReindexIT.assertExits(ReindexIT.java:429)
> at
> org.apache.jackrabbit.oak.index.ReindexIT.reindexIgnoreMissingTikaDepThrow(ReindexIT.java:144)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10524) SameNameSiblingTest: add (failing) test for getName() semantics
[ https://issues.apache.org/jira/browse/OAK-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10524. -- Fix Version/s: 1.60.0 Resolution: Fixed > SameNameSiblingTest: add (failing) test for getName() semantics > --- > > Key: OAK-10524 > URL: https://issues.apache.org/jira/browse/OAK-10524 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10524) SameNameSiblingTest: add (failing) test for getName() semantics
[ https://issues.apache.org/jira/browse/OAK-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10524: - Labels: candidate_oak_1_22 (was: ) > SameNameSiblingTest: add (failing) test for getName() semantics > --- > > Key: OAK-10524 > URL: https://issues.apache.org/jira/browse/OAK-10524 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10524) SameNameSiblingTest: add (failing) test for getName() semantics
[ https://issues.apache.org/jira/browse/OAK-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780365#comment-17780365 ] Julian Reschke commented on OAK-10524: -- trunk: [ca7ea054c2|https://github.com/apache/jackrabbit-oak/commit/ca7ea054c2f9b37260ac7f36a09186846f1fa770] > SameNameSiblingTest: add (failing) test for getName() semantics > --- > > Key: OAK-10524 > URL: https://issues.apache.org/jira/browse/OAK-10524 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.60.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10509) Build Jackrabbit/jackrabbit-oak-trunk #1228 failed
[ https://issues.apache.org/jira/browse/OAK-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780408#comment-17780408 ] Hudson commented on OAK-10509: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1246|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1246/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1246/console] > Build Jackrabbit/jackrabbit-oak-trunk #1228 failed > -- > > Key: OAK-10509 > URL: https://issues.apache.org/jira/browse/OAK-10509 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1228 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1228|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10509) Build Jackrabbit/jackrabbit-oak-trunk #1228 failed
[ https://issues.apache.org/jira/browse/OAK-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780451#comment-17780451 ] Hudson commented on OAK-10509: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1247|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1247/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1247/console] > Build Jackrabbit/jackrabbit-oak-trunk #1228 failed > -- > > Key: OAK-10509 > URL: https://issues.apache.org/jira/browse/OAK-10509 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1228 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1228|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1228/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
