[jira] [Commented] (OAK-10444) Build Jackrabbit/jackrabbit-oak-trunk #1133 failed
[ https://issues.apache.org/jira/browse/OAK-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767631#comment-17767631 ] Hudson commented on OAK-10444: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1149|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1149/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1149/console] > Build Jackrabbit/jackrabbit-oak-trunk #1133 failed > -- > > Key: OAK-10444 > URL: https://issues.apache.org/jira/browse/OAK-10444 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1133 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1133|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1133/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1133/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10453) Pipelined strategy: enforce size limit on memory taken by objects in the queue between download and transform thread
Nuno Santos created OAK-10453: - Summary: Pipelined strategy: enforce size limit on memory taken by objects in the queue between download and transform thread Key: OAK-10453 URL: https://issues.apache.org/jira/browse/OAK-10453 Project: Jackrabbit Oak Issue Type: Bug Components: indexing Reporter: Nuno Santos -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10374) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/OAK-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767535#comment-17767535 ] Manfred Baedke edited comment on OAK-10374 at 9/21/23 12:41 PM: The handling of jcr:isCheckedOut is actually broken, so this will be covered by OAK-10377. trunk: [f8a06bc2|https://github.com/apache/jackrabbit-oak/commit/f8a06bc25865c7a8961b72118f4dc90c92b93651] was (Author: baedke): trunk: [f8a06bc2|https://github.com/apache/jackrabbit-oak/commit/f8a06bc25865c7a8961b72118f4dc90c92b93651] > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: OAK-10374 > URL: https://issues.apache.org/jira/browse/OAK-10374 > Project: Jackrabbit Oak > Issue Type: Task > Components: jcr >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10452) Indexing job/regex filtering: getting ancestors nodes of filtered path incorrectly does a full col scan on Mongo
Nuno Santos created OAK-10452:
-
Summary: Indexing job/regex filtering: getting ancestors nodes of
filtered path incorrectly does a full col scan on Mongo
Key: OAK-10452
URL: https://issues.apache.org/jira/browse/OAK-10452
Project: Jackrabbit Oak
Issue Type: Improvement
Components: indexing
Reporter: Nuno Santos
In the PIPELINED strategy of the indexing job, when regex path filtering is
enabled, the job does two queries to Mongo:
* Download the ancestors of the base path (eg., {{0:/}}, {{1:/p1}},
{{2:/p1/p2}}).
* Download all the children of the base path (eg., {{???:/p1/p2/*}})
The first query returns only a few results so it should use the index on
{{_id}}. However, to deal with the rare case where the path is a long path and
the {{_id}} field is actually a hash instead of the path, the query for the
ancestors is also searching for matches on the {{_path}} field, which will be
set if {{_id}} is an hash. The issue here is that {{_path}} is not indexed, so
the first query reverts to a full col scan, which is much slower than an index
scan for the handful of ancestors. This negates most or even all of the gains
of using regex filtering.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10377) Checked-out state of non-versionable nodes is not handled correctly
[ https://issues.apache.org/jira/browse/OAK-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke resolved OAK-10377. -- Resolution: Fixed > Checked-out state of non-versionable nodes is not handled correctly > --- > > Key: OAK-10377 > URL: https://issues.apache.org/jira/browse/OAK-10377 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > > The implementation always uses the value of the property jcr:isCheckedOut if > it's present, but it also needs to check if the node is actually versionable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10377) Checked-out state of non-versionable nodes is not handled correctly
[ https://issues.apache.org/jira/browse/OAK-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767540#comment-17767540 ] Manfred Baedke commented on OAK-10377: -- trunk: [f8a06bc2|https://github.com/apache/jackrabbit-oak/commit/f8a06bc25865c7a8961b72118f4dc90c92b93651] > Checked-out state of non-versionable nodes is not handled correctly > --- > > Key: OAK-10377 > URL: https://issues.apache.org/jira/browse/OAK-10377 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > > The implementation always uses the value of the property jcr:isCheckedOut if > it's present, but it also needs to check if the node is actually versionable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10374) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/OAK-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke resolved OAK-10374. -- Resolution: Fixed > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: OAK-10374 > URL: https://issues.apache.org/jira/browse/OAK-10374 > Project: Jackrabbit Oak > Issue Type: Task > Components: jcr >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10374) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/OAK-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10374: - Fix Version/s: 1.58.0 > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: OAK-10374 > URL: https://issues.apache.org/jira/browse/OAK-10374 > Project: Jackrabbit Oak > Issue Type: Task > Components: jcr >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10377) Checked-out state of non-versionable nodes is not handled correctly
[ https://issues.apache.org/jira/browse/OAK-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10377: - Fix Version/s: 1.58.0 > Checked-out state of non-versionable nodes is not handled correctly > --- > > Key: OAK-10377 > URL: https://issues.apache.org/jira/browse/OAK-10377 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.58.0 > > > The implementation always uses the value of the property jcr:isCheckedOut if > it's present, but it also needs to check if the node is actually versionable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10374) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/OAK-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767535#comment-17767535 ] Manfred Baedke commented on OAK-10374: -- trunk: [f8a06bc2|https://github.com/apache/jackrabbit-oak/commit/f8a06bc25865c7a8961b72118f4dc90c92b93651] > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: OAK-10374 > URL: https://issues.apache.org/jira/browse/OAK-10374 > Project: Jackrabbit Oak > Issue Type: Task > Components: jcr >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10451) UserPrincipalProvider may cause many conflicts when under load
Nicola Scendoni created OAK-10451: - Summary: UserPrincipalProvider may cause many conflicts when under load Key: OAK-10451 URL: https://issues.apache.org/jira/browse/OAK-10451 Project: Jackrabbit Oak Issue Type: Bug Reporter: Nicola Scendoni UserPrincipalProvider can be configured to periodically cache group membership by writing group principals on a rep:cache node. This will result in thundering herd problem when the system is under load and the expiration time for the cache is reached. Incoming requests that authenticate concurrently will all try to refresh the cache and cause conflicts because each request tries to set a new expiration time that is slightly different from the others. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10450) Bump testcontainers dependency to v1.19.0
[ https://issues.apache.org/jira/browse/OAK-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767491#comment-17767491 ] Fabrizio Fortino commented on OAK-10450: + use of latest toxiproxy image (2.6.0) which has multi arch support > Bump testcontainers dependency to v1.19.0 > - > > Key: OAK-10450 > URL: https://issues.apache.org/jira/browse/OAK-10450 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: parent >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10450) Bump testcontainers dependency to v1.19.0
[ https://issues.apache.org/jira/browse/OAK-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino updated OAK-10450: --- Fix Version/s: (was: 1.54.0) > Bump testcontainers dependency to v1.19.0 > - > > Key: OAK-10450 > URL: https://issues.apache.org/jira/browse/OAK-10450 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: parent >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10450) Bump testcontainers dependency to v1.19.0
Fabrizio Fortino created OAK-10450: -- Summary: Bump testcontainers dependency to v1.19.0 Key: OAK-10450 URL: https://issues.apache.org/jira/browse/OAK-10450 Project: Jackrabbit Oak Issue Type: Improvement Components: parent Reporter: Fabrizio Fortino Assignee: Fabrizio Fortino Fix For: 1.54.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10444) Build Jackrabbit/jackrabbit-oak-trunk #1133 failed
[ https://issues.apache.org/jira/browse/OAK-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767479#comment-17767479 ] Hudson commented on OAK-10444: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1148|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1148/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1148/console] > Build Jackrabbit/jackrabbit-oak-trunk #1133 failed > -- > > Key: OAK-10444 > URL: https://issues.apache.org/jira/browse/OAK-10444 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1133 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1133|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1133/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1133/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10449) oak-solr-osgi embeds vulnerable Zookeeper
[ https://issues.apache.org/jira/browse/OAK-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-10449. Fix Version/s: 1.58.0 Resolution: Fixed > oak-solr-osgi embeds vulnerable Zookeeper > - > > Key: OAK-10449 > URL: https://issues.apache.org/jira/browse/OAK-10449 > Project: Jackrabbit Oak > Issue Type: Task > Components: indexing >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.58.0 > > > This artifact embeds Apache ZooKeeper 3.4.10 which contains the following > vulnerabilitie(s): > * *BDSA-2013-0048* in version 3.4.10 (CVSS 7.5 High): Apache ZooKeeper > contains an information disclosure vulnerability due to a missing permission > check within the `getACL` command. An attacker could exploit this to obtain > hashes for authentication, if Digest Authentication is in use. > * *CVE-2020-10663* in version 3.4.10 (CVSS 7.5 High): The JSON gem through > 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 > through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite > similar to CVE-2013-0269, but does not rely on poor garbage-collection > behavior within Ruby. Specifically, use of JSON parsing methods can lead to > creation of a malicious object within the interpreter, with adverse effects > that are application-dependent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10432) DocumentStoreIndexerIT failures
[
https://issues.apache.org/jira/browse/OAK-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-10432:
---
Priority: Major (was: Minor)
These tests are still failing. Recent failures I noticed
https://ci-builds.apache.org/blue/organizations/jenkins/Jackrabbit%2Foak-trunk-pr/detail/issue%2Foak-10377/2/pipeline
I think the test should either be fixed or disabled.
> 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)
