[jira] [Assigned] (OAK-10680) tests failures with com.arakelian/docker-junit-rule
[ https://issues.apache.org/jira/browse/OAK-10680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned OAK-10680: Assignee: Manfred Baedke > tests failures with com.arakelian/docker-junit-rule > --- > > Key: OAK-10680 > URL: https://issues.apache.org/jira/browse/OAK-10680 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, segment-azure >Affects Versions: 1.22.18 >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Major > > Tests have started to fail, probably because the ancient version of > com.arakelian/docker-junit-rule does not work properly with recent Docker > versions. > A potential fix would be to backport OAK-10464 to the maintenance branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10680) tests failures with com.arakelian/docker-junit-rule
[ https://issues.apache.org/jira/browse/OAK-10680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10680: - Description: Tests have started to fail, probably because the ancient version of com.arakelian/docker-junit-rule does not work properly with recent Docker versions. A potential fix would be to backport OAK-10464 to the maintenance branch. was: Tests have started to fail, probably because the ancient version of com.arakelian/docker-junit-rule does not work properly with recent Docker versions. > tests failures with com.arakelian/docker-junit-rule > --- > > Key: OAK-10680 > URL: https://issues.apache.org/jira/browse/OAK-10680 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, segment-azure >Affects Versions: 1.22.18 >Reporter: Julian Reschke >Priority: Major > > Tests have started to fail, probably because the ancient version of > com.arakelian/docker-junit-rule does not work properly with recent Docker > versions. > A potential fix would be to backport OAK-10464 to the maintenance branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10680) tests failures with com.arakelian/docker-junit-rule
Julian Reschke created OAK-10680: Summary: tests failures with com.arakelian/docker-junit-rule Key: OAK-10680 URL: https://issues.apache.org/jira/browse/OAK-10680 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk, segment-azure Affects Versions: 1.22.18 Reporter: Julian Reschke Tests have started to fail, probably because the ancient version of com.arakelian/docker-junit-rule does not work properly with recent Docker versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10674) DocumentStore: verify that we could use Oak's Bloom filter
[ https://issues.apache.org/jira/browse/OAK-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822211#comment-17822211 ] Julian Reschke commented on OAK-10674: -- I had a quick look, comparing both APIs. [~thomasm] - in your impl, I need a (long) hash to check. Guava's filter takes funnel object, and we use https://www.javadoc.io/doc/com.google.guava/guava/latest/com/google/common/hash/Funnels.html#unencodedCharsFunnel(). What would be the best way to create a hash for a String? > DocumentStore: verify that we could use Oak's Bloom filter > -- > > Key: OAK-10674 > URL: https://issues.apache.org/jira/browse/OAK-10674 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk >Reporter: Julian Reschke >Priority: Major > > Test that we can use > oak-run-commons/src/main/java/org/apache/jackrabbit/oak/index/indexer/document/flatfile/analysis/utils/BloomFilter.java > (for now, by copying it over). > Then decide about where to move it, and whether API changes are desired. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10464) Use Testcontainers instead of com.arakelian:docker-junit-rule
[ https://issues.apache.org/jira/browse/OAK-10464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10464: - Labels: candidate_oak_1_22 (was: ) > Use Testcontainers instead of com.arakelian:docker-junit-rule > - > > Key: OAK-10464 > URL: https://issues.apache.org/jira/browse/OAK-10464 > Project: Jackrabbit Oak > Issue Type: Task > Components: test >Reporter: Miroslav Smiljanic >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.60.0 > > > com.arakelian:docker-junit-rule embeds Spotify docker client, and that one > has an issue running on Apple silicon > [https://github.com/spotify/dockerfile-maven/issues/394] > We should switch to Testcontainers. > [https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.56.0/oak-blob-cloud-azure/src/test/java/org/apache/jackrabbit/oak/blob/cloud/azure/blobstorage/AzuriteDockerRule.java] > > [https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.56.0/oak-store-document/src/test/java/org/apache/jackrabbit/oak/plugins/document/mongo/MongoDockerRule.java] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10679) Release Oak 1.22.19
[ https://issues.apache.org/jira/browse/OAK-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10679: - Fix Version/s: (was: OAK-10567) > Release Oak 1.22.19 > --- > > Key: OAK-10679 > URL: https://issues.apache.org/jira/browse/OAK-10679 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10679) Release Oak 1.22.19
[ https://issues.apache.org/jira/browse/OAK-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10679. -- Fix Version/s: OAK-10567 Resolution: Duplicate > Release Oak 1.22.19 > --- > > Key: OAK-10679 > URL: https://issues.apache.org/jira/browse/OAK-10679 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: OAK-10567 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OAK-10679) Release Oak 1.22.19
[ https://issues.apache.org/jira/browse/OAK-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed OAK-10679. > Release Oak 1.22.19 > --- > > Key: OAK-10679 > URL: https://issues.apache.org/jira/browse/OAK-10679 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: OAK-10567 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10679) Release Oak 1.22.19
Julian Reschke created OAK-10679: Summary: Release Oak 1.22.19 Key: OAK-10679 URL: https://issues.apache.org/jira/browse/OAK-10679 Project: Jackrabbit Oak Issue Type: Task Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10640) docs: fix external link on lucene multi words synonyms
[ https://issues.apache.org/jira/browse/OAK-10640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-10640. Fix Version/s: 1.62.0 Resolution: Fixed > docs: fix external link on lucene multi words synonyms > --- > > Key: OAK-10640 > URL: https://issues.apache.org/jira/browse/OAK-10640 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: docs, search >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10671) [Indexing job] - Improve Mongo regex query: remove condition on non-indexed _path field to speedup traversal
[
https://issues.apache.org/jira/browse/OAK-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Santos resolved OAK-10671.
---
Fix Version/s: 1.62.0
Resolution: Done
> [Indexing job] - Improve Mongo regex query: remove condition on non-indexed
> _path field to speedup traversal
>
>
> Key: OAK-10671
> URL: https://issues.apache.org/jira/browse/OAK-10671
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.62.0
>
>
> Regex path filtering currently is implemented with a condition like:
> {noformat}
> _id in [^[0-9]{1,3}:\Q/foo/bar/\E.*$] OR ('_id' in [^[0-9]{1,3}:h.*$}] AND
> _path in [^\Q/foo/bar/\E.*$]
> {noformat}
> The second condition is necessary to deal with long path documents, whose
> {{_id}} is an hash instead of the path of the document, and that have an
> additional {{_path}} property with the full path of the document. The {{_id}}
> field is part of the index used by the query, but {{_path}} is not indexed.
> So the performance of this query will be very sensitive to how many time the
> query condition can be resolved without having to lookup the value of
> {{{}_path{}}}, which requires retrieving the full document from the column
> store. If the condition can be evaluated only using the {{_id}} value, them
> if there is no match the document should not be retrieved from the column
> store.
> Unfortunately, Mongo does not seem to properly optimize this query and is
> retrieving the document from the column storage even when {{_id}} does not
> match the path /foo/bar and the _id is not in the hash format. This leads to
> very poor performance as both the index and the column store have to be fully
> read by this query.
> We can instead use the following condition:
> {noformat}
> _id in [^[0-9]{1,3}:\Q/foo/bar/\E.*$ , ^[0-9]{1,3}:h.*$}]
> {noformat}
> That is, download the document if the _id matches the path or if it is an
> hash. This has the disadvantage that it will download all long path documents
> from the repository, many of which might not be needed. However, this query
> condition only uses the _id field so it is guaranteed to be evaluated fully
> using only the data on the index. And the number of long paths documents is
> usually very small, some environments don't even have any long path
> documents, so downloading them should not take much time. And the indexing
> job will anyway reapply the filter on paths locally, to eliminate the long
> path documents which are not required by the indexing job.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OAK-10653) BasicDocumentStoreTest: handle DocumentStoreException on ds.create
[ https://issues.apache.org/jira/browse/OAK-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817684#comment-17817684 ] Julian Reschke edited comment on OAK-10653 at 2/29/24 10:33 AM: trunk: [4a9219f4be|https://github.com/apache/jackrabbit-oak/commit/4a9219f4be079f191ba486649514b3852f4005a2] was (Author: reschke): trunk: [4a9219f4be|https://github.com/apache/jackrabbit-oak-/commit/4a9219f4be079f191ba486649514b3852f4005a2] > BasicDocumentStoreTest: handle DocumentStoreException on ds.create > -- > > Key: OAK-10653 > URL: https://issues.apache.org/jira/browse/OAK-10653 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10653) BasicDocumentStoreTest: handle DocumentStoreException on ds.create
[ https://issues.apache.org/jira/browse/OAK-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10653: - Summary: BasicDocumentStoreTest: handle DocumentStoreException on ds.create (was: BasicDocumentStore: handle DocumentStoreException on ds.create) > BasicDocumentStoreTest: handle DocumentStoreException on ds.create > -- > > Key: OAK-10653 > URL: https://issues.apache.org/jira/browse/OAK-10653 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, test >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
[ https://issues.apache.org/jira/browse/OAK-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10654. -- Resolution: Abandoned > Build Jackrabbit/jackrabbit-oak-trunk #1363 failed > -- > > Key: OAK-10654 > URL: https://issues.apache.org/jira/browse/OAK-10654 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount
[
https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10655:
-
Component/s: composite
> Improve warning emitted for Unexpected changes performed on a non-default
> mount
> ---
>
> Key: OAK-10655
> URL: https://issues.apache.org/jira/browse/OAK-10655
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: composite
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently the feature provided in OAK-9208 emits WARNs like the following
> {code}
> 5.02.2024 11:46:49.748 *WARN* [ResourceResolverFactory registration]
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$ChangeReporter
> Unexpected changes (38) performed on a non-default mount. Printing at most
> 50_- /apps : Changed_-
> java.lang.RuntimeException: null
> at
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$CountingDiff.report(NonDefaultMountWriteReportingObserver.java:106)
> at
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver.contentChanged(NonDefaultMountWriteReportingObserver.java:88)
> at
> org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:51)
> at
> org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:79)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler$ObservableLockBasedScheduler.contentChanged(LockBasedScheduler.java:394)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.execute(LockBasedScheduler.java:303)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.schedule(LockBasedScheduler.java:270)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeStore.merge(SegmentNodeStore.java:211)
> at
> org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:262)
> at
> org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate$WorkspaceCopy.perform(WorkspaceDelegate.java:130)
> at
> org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate.copy(WorkspaceDelegate.java:99)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl$2.performVoid(WorkspaceImpl.java:163)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:299)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:150)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:132)
> at
> .
> {code}
> It would be useful to add a dedicated exception message to the throwable (or
> prevent logging it) and indicate that this only indicates where the JCR
> session has been committed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-10678) update gmavenplus plugin to 3.0.2
[ https://issues.apache.org/jira/browse/OAK-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10678: - Labels: candidate_oak_1_22 (was: ) > update gmavenplus plugin to 3.0.2 > - > > Key: OAK-10678 > URL: https://issues.apache.org/jira/browse/OAK-10678 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10678) update gmavenplus plugin to 3.0.2
[ https://issues.apache.org/jira/browse/OAK-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822023#comment-17822023 ] Julian Reschke commented on OAK-10678: -- trunk: [e02fee399f|https://github.com/apache/jackrabbit-oak/commit/e02fee399f202e8b289e274e8d6a85a3b9acda3a] > update gmavenplus plugin to 3.0.2 > - > > Key: OAK-10678 > URL: https://issues.apache.org/jira/browse/OAK-10678 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10678) update gmavenplus plugin to 3.0.2
[ https://issues.apache.org/jira/browse/OAK-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10678. -- Fix Version/s: 1.62.0 Resolution: Fixed > update gmavenplus plugin to 3.0.2 > - > > Key: OAK-10678 > URL: https://issues.apache.org/jira/browse/OAK-10678 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.62.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10678) update gmavenplus plugin to 3.0.2
Julian Reschke created OAK-10678: Summary: update gmavenplus plugin to 3.0.2 Key: OAK-10678 URL: https://issues.apache.org/jira/browse/OAK-10678 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
