[jira] [Created] (OAK-10822) Build Jackrabbit/jackrabbit-oak-trunk #1487 failed
Hudson created OAK-10822: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1487 failed Key: OAK-10822 URL: https://issues.apache.org/jira/browse/OAK-10822 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1487 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1487|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1487/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1487/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10817) Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed
[ https://issues.apache.org/jira/browse/OAK-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847709#comment-17847709 ] Hudson commented on OAK-10817: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures #7|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/7/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/7/console] > Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed > -- > > Key: OAK-10817 > URL: https://issues.apache.org/jira/browse/OAK-10817 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures > #3|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10818) Build Jackrabbit/jackrabbit-oak-trunk #1483 failed
[ https://issues.apache.org/jira/browse/OAK-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847699#comment-17847699 ] Hudson commented on OAK-10818: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1486|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1486/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1486/console] > Build Jackrabbit/jackrabbit-oak-trunk #1483 failed > -- > > Key: OAK-10818 > URL: https://issues.apache.org/jira/browse/OAK-10818 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1483 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1483|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-9205) Bump htmlunit from 2.35.0 to 2.43.0
[ https://issues.apache.org/jira/browse/OAK-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-9205: Component/s: webapp > Bump htmlunit from 2.35.0 to 2.43.0 > --- > > Key: OAK-9205 > URL: https://issues.apache.org/jira/browse/OAK-9205 > Project: Jackrabbit Oak > Issue Type: Task > Components: webapp >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > Fix For: 1.22.5, 1.36.0 > > > The current version presents a vulnerability issue > (https://github.com/oak-indexing/jackrabbit-oak/pull/172). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10821) webapp: bump htmlunit to 2.70.0
[ https://issues.apache.org/jira/browse/OAK-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10821: - Description: (was: The current version presents a vulnerability issue (https://github.com/oak-indexing/jackrabbit-oak/pull/172).) > webapp: bump htmlunit to 2.70.0 > --- > > Key: OAK-10821 > URL: https://issues.apache.org/jira/browse/OAK-10821 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Fabrizio Fortino >Assignee: Julian Reschke >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10821) webapp: bump htmlunit to 2.70.0
[ https://issues.apache.org/jira/browse/OAK-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned OAK-10821: Assignee: Julian Reschke (was: Fabrizio Fortino) > webapp: bump htmlunit to 2.70.0 > --- > > Key: OAK-10821 > URL: https://issues.apache.org/jira/browse/OAK-10821 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Fabrizio Fortino >Assignee: Julian Reschke >Priority: Major > > The current version presents a vulnerability issue > (https://github.com/oak-indexing/jackrabbit-oak/pull/172). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10821) webapp: bump htmlunit to 2.70.0
Julian Reschke created OAK-10821: Summary: webapp: bump htmlunit to 2.70.0 Key: OAK-10821 URL: https://issues.apache.org/jira/browse/OAK-10821 Project: Jackrabbit Oak Issue Type: Task Reporter: Fabrizio Fortino Assignee: Fabrizio Fortino Fix For: 1.22.5, 1.36.0 The current version presents a vulnerability issue (https://github.com/oak-indexing/jackrabbit-oak/pull/172). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10821) webapp: bump htmlunit to 2.70.0
[ https://issues.apache.org/jira/browse/OAK-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10821: - Fix Version/s: (was: 1.22.5) (was: 1.36.0) > webapp: bump htmlunit to 2.70.0 > --- > > Key: OAK-10821 > URL: https://issues.apache.org/jira/browse/OAK-10821 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Major > > The current version presents a vulnerability issue > (https://github.com/oak-indexing/jackrabbit-oak/pull/172). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10820) webapp: update Tomcat dependency to 9.0.89
[ https://issues.apache.org/jira/browse/OAK-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847690#comment-17847690 ] Julian Reschke commented on OAK-10820: -- trunk: [7ab4027f49|https://github.com/apache/jackrabbit-oak/commit/7ab4027f495279469290ed5fa567da94f6d037b3] > webapp: update Tomcat dependency to 9.0.89 > -- > > Key: OAK-10820 > URL: https://issues.apache.org/jira/browse/OAK-10820 > Project: Jackrabbit Oak > Issue Type: Task > Components: webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10820) webapp: update Tomcat dependency to 9.0.89
[ https://issues.apache.org/jira/browse/OAK-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10820. -- Fix Version/s: 1.64.0 Resolution: Fixed > webapp: update Tomcat dependency to 9.0.89 > -- > > Key: OAK-10820 > URL: https://issues.apache.org/jira/browse/OAK-10820 > Project: Jackrabbit Oak > Issue Type: Task > Components: webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10820) webapp: update Tomcat dependency to 9.0.89
Julian Reschke created OAK-10820: Summary: webapp: update Tomcat dependency to 9.0.89 Key: OAK-10820 URL: https://issues.apache.org/jira/browse/OAK-10820 Project: Jackrabbit Oak Issue Type: Task Components: webapp Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 1.64.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10820) webapp: update Tomcat dependency to 9.0.89
[ https://issues.apache.org/jira/browse/OAK-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10820: - Fix Version/s: (was: 1.64.0) > webapp: update Tomcat dependency to 9.0.89 > -- > > Key: OAK-10820 > URL: https://issues.apache.org/jira/browse/OAK-10820 > Project: Jackrabbit Oak > Issue Type: Task > Components: webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10819) examples: update jetty-maven-plugin to 11.0.21
[ https://issues.apache.org/jira/browse/OAK-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847678#comment-17847678 ] Julian Reschke commented on OAK-10819: -- trunk: [bd237f298d|https://github.com/apache/jackrabbit-oak/commit/bd237f298dda2945e56582c2ec411f68363eb354] > examples: update jetty-maven-plugin to 11.0.21 > -- > > Key: OAK-10819 > URL: https://issues.apache.org/jira/browse/OAK-10819 > Project: Jackrabbit Oak > Issue Type: Task > Components: examples >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-6767) Remove felix SCR annotation support from parent pom
[ https://issues.apache.org/jira/browse/OAK-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6767: Fix Version/s: 1.66.0 (was: 1.64.0) > Remove felix SCR annotation support from parent pom > --- > > Key: OAK-6767 > URL: https://issues.apache.org/jira/browse/OAK-6767 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: parent >Reporter: Robert Munteanu >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.66.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10771) Add disk cache size stats and issue warning if evicted segment has zero length
[
https://issues.apache.org/jira/browse/OAK-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10771:
-
Fix Version/s: 1.66.0
(was: 1.64.0)
> Add disk cache size stats and issue warning if evicted segment has zero length
> --
>
> Key: OAK-10771
> URL: https://issues.apache.org/jira/browse/OAK-10771
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-azure
>Affects Versions: 1.62.0
>Reporter: Axel Hanikel
>Priority: Major
> Fix For: 1.66.0
>
>
> Note: The component is actually {{segment-remote}} but that's not on the list.
> The persistent disk cache computes its size internally by adding/subtracting
> the size of added/purged segments. We would like to be able to see if that
> computation is correct, by having both the computed size and the effective
> size on disk in the metrics.
> The background for this is that in a few rare instances, the disk cache
> evicted too many items (down to almost zero) instead of the expected 65% of
> its max size.
> Also we want to make sure that no evictions happen on items that have a
> length of zero. We're not sure if that happens or not, so the change is to
> refuse eviction in that case and log a warning instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10819) examples: update jetty-maven-plugin to 11.0.21
[ https://issues.apache.org/jira/browse/OAK-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10819. -- Fix Version/s: 1.64.0 Resolution: Fixed > examples: update jetty-maven-plugin to 11.0.21 > -- > > Key: OAK-10819 > URL: https://issues.apache.org/jira/browse/OAK-10819 > Project: Jackrabbit Oak > Issue Type: Task > Components: examples >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10819) examples: update jetty-maven-plugin to 11.0.21
[ https://issues.apache.org/jira/browse/OAK-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10819: - Fix Version/s: (was: 1.62.0) (was: 1.22.20) > examples: update jetty-maven-plugin to 11.0.21 > -- > > Key: OAK-10819 > URL: https://issues.apache.org/jira/browse/OAK-10819 > Project: Jackrabbit Oak > Issue Type: Task > Components: examples >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10819) examples: update jetty-maven-plugin to 11.0.21
[ https://issues.apache.org/jira/browse/OAK-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10819: - Labels: candidate_oak_1_22 (was: ) > examples: update jetty-maven-plugin to 11.0.21 > -- > > Key: OAK-10819 > URL: https://issues.apache.org/jira/browse/OAK-10819 > Project: Jackrabbit Oak > Issue Type: Task > Components: examples >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10819) examples: update jetty-maven-plugin to 11.0.21
Julian Reschke created OAK-10819: Summary: examples: update jetty-maven-plugin to 11.0.21 Key: OAK-10819 URL: https://issues.apache.org/jira/browse/OAK-10819 Project: Jackrabbit Oak Issue Type: Task Components: examples Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 1.62.0, 1.22.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10818) Build Jackrabbit/jackrabbit-oak-trunk #1483 failed
[ https://issues.apache.org/jira/browse/OAK-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847606#comment-17847606 ] Hudson commented on OAK-10818: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1485|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1485/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1485/console] > Build Jackrabbit/jackrabbit-oak-trunk #1483 failed > -- > > Key: OAK-10818 > URL: https://issues.apache.org/jira/browse/OAK-10818 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1483 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1483|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10817) Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed
[ https://issues.apache.org/jira/browse/OAK-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847591#comment-17847591 ] Hudson commented on OAK-10817: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures #4|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/4/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/4/console] > Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed > -- > > Key: OAK-10817 > URL: https://issues.apache.org/jira/browse/OAK-10817 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures > #3|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10818) Build Jackrabbit/jackrabbit-oak-trunk #1483 failed
[ https://issues.apache.org/jira/browse/OAK-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847575#comment-17847575 ] Hudson commented on OAK-10818: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1484|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1484/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1484/console] > Build Jackrabbit/jackrabbit-oak-trunk #1483 failed > -- > > Key: OAK-10818 > URL: https://issues.apache.org/jira/browse/OAK-10818 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1483 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1483|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10818) Build Jackrabbit/jackrabbit-oak-trunk #1483 failed
Hudson created OAK-10818: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1483 failed Key: OAK-10818 URL: https://issues.apache.org/jira/browse/OAK-10818 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1483 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1483|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1483/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10816) Update spotbugs plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/OAK-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847574#comment-17847574 ] Julian Reschke commented on OAK-10816: -- trunk: [f9e1dfa80d|https://github.com/apache/jackrabbit-oak/commit/f9e1dfa80d3c762c3c4ed6a494bd2a0d66dac108] > Update spotbugs plugin to 4.8.5.0 > - > > Key: OAK-10816 > URL: https://issues.apache.org/jira/browse/OAK-10816 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10816) Update spotbugs plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/OAK-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10816: - Labels: candidate_oak_1_22 (was: ) > Update spotbugs plugin to 4.8.5.0 > - > > Key: OAK-10816 > URL: https://issues.apache.org/jira/browse/OAK-10816 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10816) Update spotbugs plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/OAK-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10816. -- Fix Version/s: 1.64.0 Resolution: Fixed > Update spotbugs plugin to 4.8.5.0 > - > > Key: OAK-10816 > URL: https://issues.apache.org/jira/browse/OAK-10816 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10817) Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed
Hudson created OAK-10817: Summary: Build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 failed Key: OAK-10817 URL: https://issues.apache.org/jira/browse/OAK-10817 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures #3|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/3/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10760) oak-core should check namespace registry consistency on startup
[ https://issues.apache.org/jira/browse/OAK-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847375#comment-17847375 ] Julian Reschke commented on OAK-10760: -- trunk: [43619290a5|https://github.com/apache/jackrabbit-oak/commit/43619290a5ebdc9c60aa9d1929f796e5033f59da] > oak-core should check namespace registry consistency on startup > --- > > Key: OAK-10760 > URL: https://issues.apache.org/jira/browse/OAK-10760 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Critical > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > The persisted namespace registry contains maps from prefix to name and vice > versa; plus all names and prefixes as multivalued string properties. > When rep:uris gets broken, ReadOnlyNamespaceRegistry may fail to check for > duplicate namespace registrations (*). > We should check the consistency of the registry upon repo startup, and > ERROR-level log issues for further analysis. Automatic repair might be > non-trivial, though. > (*) Seen in a real-world install: rep:prefixes containing 128 entries, but > rep:uris a single one (with invalid value). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10760) oak-core should check namespace registry consistency on startup
[ https://issues.apache.org/jira/browse/OAK-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10760. -- Resolution: Fixed > oak-core should check namespace registry consistency on startup > --- > > Key: OAK-10760 > URL: https://issues.apache.org/jira/browse/OAK-10760 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Critical > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > The persisted namespace registry contains maps from prefix to name and vice > versa; plus all names and prefixes as multivalued string properties. > When rep:uris gets broken, ReadOnlyNamespaceRegistry may fail to check for > duplicate namespace registrations (*). > We should check the consistency of the registry upon repo startup, and > ERROR-level log issues for further analysis. Automatic repair might be > non-trivial, though. > (*) Seen in a real-world install: rep:prefixes containing 128 entries, but > rep:uris a single one (with invalid value). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10760) oak-core should check namespace registry consistency on startup
[ https://issues.apache.org/jira/browse/OAK-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10760: - Labels: candidate_oak_1_22 (was: ) > oak-core should check namespace registry consistency on startup > --- > > Key: OAK-10760 > URL: https://issues.apache.org/jira/browse/OAK-10760 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Julian Reschke >Assignee: Manfred Baedke >Priority: Critical > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > The persisted namespace registry contains maps from prefix to name and vice > versa; plus all names and prefixes as multivalued string properties. > When rep:uris gets broken, ReadOnlyNamespaceRegistry may fail to check for > duplicate namespace registrations (*). > We should check the consistency of the registry upon repo startup, and > ERROR-level log issues for further analysis. Automatic repair might be > non-trivial, though. > (*) Seen in a real-world install: rep:prefixes containing 128 entries, but > rep:uris a single one (with invalid value). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10816) Update spotbugs plugin to 4.8.5.0
[
https://issues.apache.org/jira/browse/OAK-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10816:
-
Description: (was: Building Oak with Java 17 currently fails with:
{noformat}
[ERROR] Failed to execute goal
com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs (spotbugs) on project
oak-parent: Execution spotbugs of goal
com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs failed: Unable to
load the mojo 'spotbugs' in the plugin
'com.github.spotbugs:spotbugs-maven-plugin:3.1.11'. A required class is
missing: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
{noformat})
> Update spotbugs plugin to 4.8.5.0
> -
>
> Key: OAK-10816
> URL: https://issues.apache.org/jira/browse/OAK-10816
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
>Priority: Minor
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10816) Update spotbugs plugin to 4.8.5.0
Julian Reschke created OAK-10816:
Summary: Update spotbugs plugin to 4.8.5.0
Key: OAK-10816
URL: https://issues.apache.org/jira/browse/OAK-10816
Project: Jackrabbit Oak
Issue Type: Task
Components: parent
Reporter: Marcel Reutegger
Assignee: Julian Reschke
Fix For: 1.62.0, 1.22.20
Building Oak with Java 17 currently fails with:
{noformat}
[ERROR] Failed to execute goal
com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs (spotbugs) on project
oak-parent: Execution spotbugs of goal
com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs failed: Unable to
load the mojo 'spotbugs' in the plugin
'com.github.spotbugs:spotbugs-maven-plugin:3.1.11'. A required class is
missing: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-10816) Update spotbugs plugin to 4.8.5.0
[
https://issues.apache.org/jira/browse/OAK-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10816:
-
Fix Version/s: (was: 1.62.0)
(was: 1.22.20)
> Update spotbugs plugin to 4.8.5.0
> -
>
> Key: OAK-10816
> URL: https://issues.apache.org/jira/browse/OAK-10816
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
>Priority: Minor
>
> Building Oak with Java 17 currently fails with:
> {noformat}
> [ERROR] Failed to execute goal
> com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs (spotbugs) on
> project oak-parent: Execution spotbugs of goal
> com.github.spotbugs:spotbugs-maven-plugin:3.1.11:spotbugs failed: Unable to
> load the mojo 'spotbugs' in the plugin
> 'com.github.spotbugs:spotbugs-maven-plugin:3.1.11'. A required class is
> missing: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10815) Update jacoco plugin to 0.8.12
[ https://issues.apache.org/jira/browse/OAK-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847349#comment-17847349 ] Julian Reschke commented on OAK-10815: -- trunk: [1f25d6fc4a|https://github.com/apache/jackrabbit-oak/commit/1f25d6fc4a547951923274b054bca2f8bbdd0de1] > Update jacoco plugin to 0.8.12 > -- > > Key: OAK-10815 > URL: https://issues.apache.org/jira/browse/OAK-10815 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > Jacoco 0.8.8 officially supports Java 17. Oak is currently using 0.8.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10815) Update jacoco plugin to 0.8.12
[ https://issues.apache.org/jira/browse/OAK-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10815: - Labels: candidate_oak_1_22 (was: ) > Update jacoco plugin to 0.8.12 > -- > > Key: OAK-10815 > URL: https://issues.apache.org/jira/browse/OAK-10815 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > Jacoco 0.8.8 officially supports Java 17. Oak is currently using 0.8.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10815) Update jacoco plugin to 0.8.12
[ https://issues.apache.org/jira/browse/OAK-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10815. -- Fix Version/s: 1.64.0 Resolution: Fixed > Update jacoco plugin to 0.8.12 > -- > > Key: OAK-10815 > URL: https://issues.apache.org/jira/browse/OAK-10815 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.64.0 > > > Jacoco 0.8.8 officially supports Java 17. Oak is currently using 0.8.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10815) Update jacoco plugin to 0.8.12
[ https://issues.apache.org/jira/browse/OAK-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10815: - Fix Version/s: (was: 1.62.0) (was: 1.22.20) > Update jacoco plugin to 0.8.12 > -- > > Key: OAK-10815 > URL: https://issues.apache.org/jira/browse/OAK-10815 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Marcel Reutegger >Assignee: Julian Reschke >Priority: Minor > > Jacoco 0.8.8 officially supports Java 17. Oak is currently using 0.8.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10815) Update jacoco plugin to 0.8.12
Julian Reschke created OAK-10815: Summary: Update jacoco plugin to 0.8.12 Key: OAK-10815 URL: https://issues.apache.org/jira/browse/OAK-10815 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: Marcel Reutegger Assignee: Julian Reschke Fix For: 1.62.0, 1.22.20 Jacoco 0.8.8 officially supports Java 17. Oak is currently using 0.8.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10814) Tar file recovery still fails with SNFE in some cases.
[
https://issues.apache.org/jira/browse/OAK-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847333#comment-17847333
]
Miroslav Smiljanic commented on OAK-10814:
--
Hi [~ahanikel] , I have merged PR with the proposed change. Thank you for
contributing.
> Tar file recovery still fails with SNFE in some cases.
> --
>
> Key: OAK-10814
> URL: https://issues.apache.org/jira/browse/OAK-10814
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.62.0
>Reporter: Axel Hanikel
>Assignee: Miroslav Smiljanic
>Priority: Major
> Fix For: 1.64.0
>
>
> {noformat}
> 13.05.2024 06:59:56.357 WARN[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarReader Unable to load
> index of file data21604a.tar: Unrecognized magic number
> 13.05.2024 06:59:56.369 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Backing up
> data21604a.tar to data21604a.tar.bak
> 13.05.2024 06:59:56.372 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Regenerating tar file
> data21604a.tar
> 13.05.2024 06:59:56.439 ERROR [FelixStartLevel]
> org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment
> not found: a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652. SegmentId age=18ms
> org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment
> a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652 not found
> at
> org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:297)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.lambda$readSegment$10(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.lambda$getSegment$0(SegmentCache.java:163)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4938)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3576)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2191)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.get(LocalCache.java:2081)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache.get(LocalCache.java:4019)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4933)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.getSegment(SegmentCache.java:160)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.readSegment(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:153)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:71)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:99)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:92)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.read(SegmentStream.java:166)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.read(ByteStreams.java:934)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:802)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:786)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.getString(SegmentStream.java:105)
> [
[jira] [Resolved] (OAK-10814) Tar file recovery still fails with SNFE in some cases.
[
https://issues.apache.org/jira/browse/OAK-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Smiljanic resolved OAK-10814.
--
Fix Version/s: 1.64.0
Resolution: Fixed
> Tar file recovery still fails with SNFE in some cases.
> --
>
> Key: OAK-10814
> URL: https://issues.apache.org/jira/browse/OAK-10814
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.62.0
>Reporter: Axel Hanikel
>Assignee: Miroslav Smiljanic
>Priority: Major
> Fix For: 1.64.0
>
>
> {noformat}
> 13.05.2024 06:59:56.357 WARN[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarReader Unable to load
> index of file data21604a.tar: Unrecognized magic number
> 13.05.2024 06:59:56.369 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Backing up
> data21604a.tar to data21604a.tar.bak
> 13.05.2024 06:59:56.372 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Regenerating tar file
> data21604a.tar
> 13.05.2024 06:59:56.439 ERROR [FelixStartLevel]
> org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment
> not found: a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652. SegmentId age=18ms
> org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment
> a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652 not found
> at
> org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:297)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.lambda$readSegment$10(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.lambda$getSegment$0(SegmentCache.java:163)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4938)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3576)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2191)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.get(LocalCache.java:2081)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache.get(LocalCache.java:4019)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4933)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.getSegment(SegmentCache.java:160)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.readSegment(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:153)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:71)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:99)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:92)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.read(SegmentStream.java:166)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.read(ByteStreams.java:934)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:802)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:786)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.getString(SegmentStream.java:105)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackra
[jira] [Assigned] (OAK-10814) Tar file recovery still fails with SNFE in some cases.
[
https://issues.apache.org/jira/browse/OAK-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Smiljanic reassigned OAK-10814:
Assignee: Miroslav Smiljanic
> Tar file recovery still fails with SNFE in some cases.
> --
>
> Key: OAK-10814
> URL: https://issues.apache.org/jira/browse/OAK-10814
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.62.0
>Reporter: Axel Hanikel
>Assignee: Miroslav Smiljanic
>Priority: Major
>
> {noformat}
> 13.05.2024 06:59:56.357 WARN[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarReader Unable to load
> index of file data21604a.tar: Unrecognized magic number
> 13.05.2024 06:59:56.369 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Backing up
> data21604a.tar to data21604a.tar.bak
> 13.05.2024 06:59:56.372 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Regenerating tar file
> data21604a.tar
> 13.05.2024 06:59:56.439 ERROR [FelixStartLevel]
> org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment
> not found: a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652. SegmentId age=18ms
> org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment
> a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652 not found
> at
> org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:297)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.lambda$readSegment$10(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.lambda$getSegment$0(SegmentCache.java:163)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4938)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3576)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2191)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.get(LocalCache.java:2081)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache.get(LocalCache.java:4019)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4933)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.getSegment(SegmentCache.java:160)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.readSegment(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:153)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:71)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:99)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:92)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.read(SegmentStream.java:166)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.read(ByteStreams.java:934)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:802)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:786)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.getString(SegmentStream.java:105)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.Segment.readString(Segment.java:467)
> [org
[jira] [Commented] (OAK-10814) Tar file recovery still fails with SNFE in some cases.
[
https://issues.apache.org/jira/browse/OAK-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847250#comment-17847250
]
Axel Hanikel commented on OAK-10814:
Proposed patch: https://github.com/apache/jackrabbit-oak/pull/1468
Putting recovered segments in the SegmentCache makes them available during
remaining recovery operations. In the case of the blobId map, this works as
long as the blobId is stored in a data segment and not in a raw segment (raw
segment's aren't cached). But the blobIds shouldn't become that large in
practice.
> Tar file recovery still fails with SNFE in some cases.
> --
>
> Key: OAK-10814
> URL: https://issues.apache.org/jira/browse/OAK-10814
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
>Affects Versions: 1.62.0
>Reporter: Axel Hanikel
>Priority: Major
>
> {noformat}
> 13.05.2024 06:59:56.357 WARN[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.SegmentTarReader Unable to load
> index of file data21604a.tar: Unrecognized magic number
> 13.05.2024 06:59:56.369 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Backing up
> data21604a.tar to data21604a.tar.bak
> 13.05.2024 06:59:56.372 INFO[FelixStartLevel]
> org.apache.jackrabbit.oak.segment.file.tar.TarReader Regenerating tar file
> data21604a.tar
> 13.05.2024 06:59:56.439 ERROR [FelixStartLevel]
> org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment
> not found: a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652. SegmentId age=18ms
> org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment
> a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652 not found
> at
> org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:297)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.lambda$readSegment$10(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.lambda$getSegment$0(SegmentCache.java:163)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4938)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3576)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2191)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.get(LocalCache.java:2081)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache.get(LocalCache.java:4019)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4933)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.getSegment(SegmentCache.java:160)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.file.FileStore.readSegment(FileStore.java:512)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:153)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:71)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:99)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:92)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.oak.segment.SegmentStream.read(SegmentStream.java:166)
> [org.apache.jackrabbit.oak-segment-tar:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.read(ByteStreams.java:934)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:802)
> [org.apache.jackrabbit.guava:1.62.0]
> at
> org.apache.
[jira] [Created] (OAK-10814) Tar file recovery still fails with SNFE in some cases.
Axel Hanikel created OAK-10814:
--
Summary: Tar file recovery still fails with SNFE in some cases.
Key: OAK-10814
URL: https://issues.apache.org/jira/browse/OAK-10814
Project: Jackrabbit Oak
Issue Type: Bug
Components: segment-tar
Affects Versions: 1.62.0
Reporter: Axel Hanikel
{noformat}
13.05.2024 06:59:56.357 WARN[FelixStartLevel]
org.apache.jackrabbit.oak.segment.file.tar.SegmentTarReader Unable to load
index of file data21604a.tar: Unrecognized magic number
13.05.2024 06:59:56.369 INFO[FelixStartLevel]
org.apache.jackrabbit.oak.segment.file.tar.TarReader Backing up data21604a.tar
to data21604a.tar.bak
13.05.2024 06:59:56.372 INFO[FelixStartLevel]
org.apache.jackrabbit.oak.segment.file.tar.TarReader Regenerating tar file
data21604a.tar
13.05.2024 06:59:56.439 ERROR [FelixStartLevel]
org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment not
found: a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652. SegmentId age=18ms
org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment
a4ad6e4b-93dc-4e09-ad0d-ab99a7f93652 not found
at
org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:297)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.file.FileStore.lambda$readSegment$10(FileStore.java:512)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.lambda$getSegment$0(SegmentCache.java:163)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4938)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3576)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2318)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2191)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$Segment.get(LocalCache.java:2081)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache.get(LocalCache.java:4019)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4933)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentCache$NonEmptyCache.getSegment(SegmentCache.java:160)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.file.FileStore.readSegment(FileStore.java:512)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentId.getSegment(SegmentId.java:153)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at org.apache.jackrabbit.oak.segment.Record.getSegment(Record.java:71)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:99)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.ListRecord.getEntries(ListRecord.java:92)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentStream.read(SegmentStream.java:166)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.guava.common.io.ByteStreams.read(ByteStreams.java:934)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:802)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.guava.common.io.ByteStreams.readFully(ByteStreams.java:786)
[org.apache.jackrabbit.guava:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentStream.getString(SegmentStream.java:105)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.Segment.readString(Segment.java:467)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
at
org.apache.jackrabbit.oak.segment.SegmentBlob.readLongBlobId(SegmentBlob.java:248)
[org.apache.jackrabbit.oak-segment-tar:1.62.0]
{noformat}
The reason seems to be that the long blobId string is stored behind a list
record, where the elements are stored in yet a different segment, which is then
loaded in the normal way, i.e. bypassing the recovery map added in OAK-10636.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10813) Improve performance of Oak-mongo.js function to remove/list nodes
Rishabh Daim created OAK-10813: -- Summary: Improve performance of Oak-mongo.js function to remove/list nodes Key: OAK-10813 URL: https://issues.apache.org/jira/browse/OAK-10813 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Rishabh Daim Assignee: Rishabh Daim Functions *oak.removeDescendantsAndSelf()* & *oak.listRootTempNodes()* & *oak.removeRootTempNodes()* are very slow. One thing that can be done to improve their performance is that we could use projections to fetch only *_id*, since we only need *_id* to remove them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-8848) Impossible to replace a mix:versionable by a different mix:versionable
[
https://issues.apache.org/jira/browse/OAK-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847205#comment-17847205
]
Julian Reschke commented on OAK-8848:
-
Can we start with a subtask to create a reproducable test and mark that as
"@Ignore".
> Impossible to replace a mix:versionable by a different mix:versionable
> --
>
> Key: OAK-8848
> URL: https://issues.apache.org/jira/browse/OAK-8848
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
>Affects Versions: 1.16.0
> Environment: The problem occurred from within Sling (Starter 11)
> using oak 1.16.0.
>Reporter: Hans-Peter Stoerr
>Priority: Minor
>
> If you delete a node with mixin mix:versionable and move another node with
> the same mixin in its place (that is, it now has the very same path), you get
> a ConstraintViolationException that complains that you are changing protected
> properties. Thus, this operation is impossible to perform within one
> transaction. But splitting it into two transactions is risky in many cases.
> It seems there is a mechanism that checks for changes of protected
> properties, and ignores that this is now a different node.
> If you have two nodes /somewhere/1 and /somewhere/2 which both are
> nt:unstructured and have mix:versionable, the following code triggers an
> exception but shouldn't:
> session.removeItem("/somewhere/2");
> session.move("/somewhere/1", "/somewhere/2");
> session.save();
> The actual stacktrace thrown is:
> javax.jcr.nodetype.ConstraintViolationException: OakConstraint0100: Property
> is protected: jcr:versionHistory
> at
> org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:226)
> at
> org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:213)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.newRepositoryException(SessionDelegate.java:669)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.save(SessionDelegate.java:495)
> at
> org.apache.jackrabbit.oak.jcr.session.SessionImpl$8.performVoid(SessionImpl.java:420)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:273)
> at
> org.apache.jackrabbit.oak.jcr.session.SessionImpl.save(SessionImpl.java:417)
> at
> org.apache.sling.jcr.oak.server.internal.TcclWrappingJackrabbitSession.save(TcclWrappingJackrabbitSession.java:212)
> at
> org.apache.jsp.apps.composum.prototype.assets.pagesintegration.hpsx.hpsx_jsp._jspService(hpsx_jsp.java:115)
> at
> org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> (irrelevant sling stuff omitted)
> Caused by: org.apache.jackrabbit.oak.api.CommitFailedException:
> OakConstraint0100: Property is protected: jcr:versionHistory
> at
> org.apache.jackrabbit.oak.plugins.version.VersionEditor.throwProtected(VersionEditor.java:257)
> at
> org.apache.jackrabbit.oak.plugins.version.VersionEditor.propertyChanged(VersionEditor.java:152)
> at
> org.apache.jackrabbit.oak.spi.commit.VisibleEditor.propertyChanged(VisibleEditor.java:73)
> at
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.propertyChanged(EditorDiff.java:92)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.compareProperties(SegmentNodeState.java:664)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:558)
> at
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.childNodeChanged(EditorDiff.java:147)
> at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:495)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:651)
> at
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.childNodeChanged(EditorDiff.java:147)
> at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:422)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:651)
> at
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.childNodeChanged(EditorDiff.java:147)
> at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:422)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:651)
> at
> org.apache.jackrabbit.oak.spi.commit.EditorDiff.childNodeChanged(EditorDiff.java:147)
> at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:422)
> at
> org.apach
[jira] [Created] (OAK-10812) DocumentNodeStore#diffManyChildren(...) may produce incorrect results in readonly mode
Manfred Baedke created OAK-10812: Summary: DocumentNodeStore#diffManyChildren(...) may produce incorrect results in readonly mode Key: OAK-10812 URL: https://issues.apache.org/jira/browse/OAK-10812 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk Reporter: Manfred Baedke Assignee: Manfred Baedke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10811) oak-search-elastic: reduce contention in IndexTracker
Fabrizio Fortino created OAK-10811: -- Summary: oak-search-elastic: reduce contention in IndexTracker Key: OAK-10811 URL: https://issues.apache.org/jira/browse/OAK-10811 Project: Jackrabbit Oak Issue Type: Improvement Components: indexing Reporter: Fabrizio Fortino Assignee: Fabrizio Fortino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10804) Indexing job: optimize check for hidden nodes
[
https://issues.apache.org/jira/browse/OAK-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Santos resolved OAK-10804.
---
Fix Version/s: 1.64.0
Resolution: Done
> Indexing job: optimize check for hidden nodes
> -
>
> Key: OAK-10804
> URL: https://issues.apache.org/jira/browse/OAK-10804
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
> Fix For: 1.64.0
>
>
> While downloading the repository from Mongo, the indexing job has to discard
> hidden entries. This is being done by a call to
> {{{}NodeStateUtils.isHiddenPath(){}}}. This call is rather expensive, as it
> creates an iterator over the path segments, which requires creating a new
> string for each path segment. As the indexing job has to check every entry to
> verify if it is hidden, this creates a significant overhead.
> The implementation of checking for hidden paths can be replaced by a simple
> search for {{"/:"}} in the string representing the path, which requires no
> object allocation and should therefore be much faster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10809) Build Jackrabbit/jackrabbit-oak-trunk #1476 failed
[ https://issues.apache.org/jira/browse/OAK-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846946#comment-17846946 ] Hudson commented on OAK-10809: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1477|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1477/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1477/console] > Build Jackrabbit/jackrabbit-oak-trunk #1476 failed > -- > > Key: OAK-10809 > URL: https://issues.apache.org/jira/browse/OAK-10809 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1476 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1476|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1476/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1476/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10810) Remove redundant call to StringCache.get in Path.fromString()
[ https://issues.apache.org/jira/browse/OAK-10810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nuno Santos resolved OAK-10810. --- Fix Version/s: 1.64.0 Resolution: Done > Remove redundant call to StringCache.get in Path.fromString() > - > > Key: OAK-10810 > URL: https://issues.apache.org/jira/browse/OAK-10810 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10778) Indexing job: support parallel download from MongoDB with two connections in Pipelined strategy
[
https://issues.apache.org/jira/browse/OAK-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-10778.
--
Resolution: Fixed
> Indexing job: support parallel download from MongoDB with two connections in
> Pipelined strategy
> ---
>
> Key: OAK-10778
> URL: https://issues.apache.org/jira/browse/OAK-10778
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Assignee: Nuno Santos
>Priority: Major
> Fix For: 1.64.0
>
>
> The current version of the Pipelined download strategy uses a single
> connection/thread to download from MongoDB. We can further increase the
> download speed by using an additional MongoDB connection. A Mongo deployment
> has 1 primary and 2 secondaries, so in principle we could have 1 connection
> to each secondary, effectively doubling the download speed.
> There are a few points to observe:
> - Connections should go to different secondaries. If both connections go to
> the same secondary, there's a high change that they will be limited by what a
> single replica can provide and of overloading that replica. So each secondary
> should have one and only one connection.
> - How to partition the range of documents to download between two threads.
> We are already downloading from Mongo in order of {{(_modified, _id)}}. A
> simple and effective partition strategy for 2 connections is for one to
> download in ascending and the other in descending order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10808) PipelinedMongoConnectionFailureIT should not fail if Mongo is not available
[ https://issues.apache.org/jira/browse/OAK-10808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10808. -- Fix Version/s: 1.64.0 Resolution: Fixed > PipelinedMongoConnectionFailureIT should not fail if Mongo is not available > --- > > Key: OAK-10808 > URL: https://issues.apache.org/jira/browse/OAK-10808 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Critical > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10810) Remove redundant call to StringCache.get in Path.fromString()
[ https://issues.apache.org/jira/browse/OAK-10810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10810: - Labels: candidate_oak_1_22 (was: ) > Remove redundant call to StringCache.get in Path.fromString() > - > > Key: OAK-10810 > URL: https://issues.apache.org/jira/browse/OAK-10810 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Labels: candidate_oak_1_22 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10810) Remove redundant call to StringCache.get in Path.fromString()
Nuno Santos created OAK-10810: - Summary: Remove redundant call to StringCache.get in Path.fromString() Key: OAK-10810 URL: https://issues.apache.org/jira/browse/OAK-10810 Project: Jackrabbit Oak Issue Type: Improvement Components: indexing Reporter: Nuno Santos -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10809) Build Jackrabbit/jackrabbit-oak-trunk #1476 failed
Hudson created OAK-10809: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1476 failed Key: OAK-10809 URL: https://issues.apache.org/jira/browse/OAK-10809 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1476 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1476|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1476/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1476/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10778) Indexing job: support parallel download from MongoDB with two connections in Pipelined strategy
[
https://issues.apache.org/jira/browse/OAK-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846831#comment-17846831
]
Nuno Santos commented on OAK-10778:
---
Fix here:
[https://github.com/apache/jackrabbit-oak/pull/1463]
> Indexing job: support parallel download from MongoDB with two connections in
> Pipelined strategy
> ---
>
> Key: OAK-10778
> URL: https://issues.apache.org/jira/browse/OAK-10778
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Assignee: Nuno Santos
>Priority: Major
> Fix For: 1.64.0
>
>
> The current version of the Pipelined download strategy uses a single
> connection/thread to download from MongoDB. We can further increase the
> download speed by using an additional MongoDB connection. A Mongo deployment
> has 1 primary and 2 secondaries, so in principle we could have 1 connection
> to each secondary, effectively doubling the download speed.
> There are a few points to observe:
> - Connections should go to different secondaries. If both connections go to
> the same secondary, there's a high change that they will be limited by what a
> single replica can provide and of overloading that replica. So each secondary
> should have one and only one connection.
> - How to partition the range of documents to download between two threads.
> We are already downloading from Mongo in order of {{(_modified, _id)}}. A
> simple and effective partition strategy for 2 connections is for one to
> download in ascending and the other in descending order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10808) PipelinedMongoConnectionFailureIT should not fail if Mongo is not available
Nuno Santos created OAK-10808: - Summary: PipelinedMongoConnectionFailureIT should not fail if Mongo is not available Key: OAK-10808 URL: https://issues.apache.org/jira/browse/OAK-10808 Project: Jackrabbit Oak Issue Type: Improvement Components: indexing Reporter: Nuno Santos -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10719) oak-lucene uses Lucene version that can throw a StackOverflowException
[ https://issues.apache.org/jira/browse/OAK-10719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846798#comment-17846798 ] Julian Reschke commented on OAK-10719: -- Two subtasks resolved: OAK-10786 and OAK-10787. > oak-lucene uses Lucene version that can throw a StackOverflowException > -- > > Key: OAK-10719 > URL: https://issues.apache.org/jira/browse/OAK-10719 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > See <https://github.com/apache/lucene/issues/11537>. > Analysis so far: > - oak-lucene uses lucene-core (4.7.2) (see OAK-10716); that version has > reached EOL a long time ago > - the lucene version can in some cases throw a StackOverflowException, see > OAK-10713 > - oak-lucene *embeds* and *exports* lucene-core > - update to version >= 4.8 non-trivial due to backwards compat breakage > Work in <https://github.com/reschke/jackrabbit-oak-lucene/tree/lucene-poc>: > - inlined lucene-core as of git tag "releases/lucene-solr/4.7.2" into > oak-lucene > - fixed two JDK11 compile issues (potentially uninitialized vars in finally > block) > - backported fix from https://github.com/apache/lucene/issues/11537 > - enable test added in OAK-10713 > - ran Oak integration tests > Open questions: > - Lucene 4.7.2 builds with ant/ivy - does it make sense to try to replicate > that > - should we ask Lucene team for a public release (might be hard sell) > - alternatively, as tried here, inline source code into oak-lucene (maybe add > explainers to all source files) > - do we need to adopt the lucene test suite as well? > - lucene-core dependencies in other Oak modules to be checked (seems mostly > for tests, or for run modules) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10719) oak-lucene uses Lucene version that can throw a StackOverflowException
[ https://issues.apache.org/jira/browse/OAK-10719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10719. -- Resolution: Fixed > oak-lucene uses Lucene version that can throw a StackOverflowException > -- > > Key: OAK-10719 > URL: https://issues.apache.org/jira/browse/OAK-10719 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > > See <https://github.com/apache/lucene/issues/11537>. > Analysis so far: > - oak-lucene uses lucene-core (4.7.2) (see OAK-10716); that version has > reached EOL a long time ago > - the lucene version can in some cases throw a StackOverflowException, see > OAK-10713 > - oak-lucene *embeds* and *exports* lucene-core > - update to version >= 4.8 non-trivial due to backwards compat breakage > Work in <https://github.com/reschke/jackrabbit-oak-lucene/tree/lucene-poc>: > - inlined lucene-core as of git tag "releases/lucene-solr/4.7.2" into > oak-lucene > - fixed two JDK11 compile issues (potentially uninitialized vars in finally > block) > - backported fix from https://github.com/apache/lucene/issues/11537 > - enable test added in OAK-10713 > - ran Oak integration tests > Open questions: > - Lucene 4.7.2 builds with ant/ivy - does it make sense to try to replicate > that > - should we ask Lucene team for a public release (might be hard sell) > - alternatively, as tried here, inline source code into oak-lucene (maybe add > explainers to all source files) > - do we need to adopt the lucene test suite as well? > - lucene-core dependencies in other Oak modules to be checked (seems mostly > for tests, or for run modules) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10787) oak-lucene: backport fix for lucene-core vulnerability
[ https://issues.apache.org/jira/browse/OAK-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846797#comment-17846797 ] Julian Reschke commented on OAK-10787: -- trunk: [283a1d7fea|https://github.com/apache/jackrabbit-oak/commit/283a1d7fea23fdceff8dda6e88b059d6990eff09] > oak-lucene: backport fix for lucene-core vulnerability > -- > > Key: OAK-10787 > URL: https://issues.apache.org/jira/browse/OAK-10787 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10787) oak-lucene: backport fix for lucene-core vulnerability
[ https://issues.apache.org/jira/browse/OAK-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10787: - Labels: candidate_oak_1_22 (was: ) > oak-lucene: backport fix for lucene-core vulnerability > -- > > Key: OAK-10787 > URL: https://issues.apache.org/jira/browse/OAK-10787 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10787) oak-lucene: backport fix for lucene-core vulnerability
[ https://issues.apache.org/jira/browse/OAK-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10787. -- Resolution: Fixed > oak-lucene: backport fix for lucene-core vulnerability > -- > > Key: OAK-10787 > URL: https://issues.apache.org/jira/browse/OAK-10787 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10805) Build Jackrabbit/jackrabbit-oak-trunk #1472 failed
[ https://issues.apache.org/jira/browse/OAK-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846746#comment-17846746 ] Hudson commented on OAK-10805: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1475|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1475/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1475/console] > Build Jackrabbit/jackrabbit-oak-trunk #1472 failed > -- > > Key: OAK-10805 > URL: https://issues.apache.org/jira/browse/OAK-10805 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1472 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1472|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10778) Indexing job: support parallel download from MongoDB with two connections in Pipelined strategy
[
https://issues.apache.org/jira/browse/OAK-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned OAK-10778:
Assignee: Nuno Santos
> Indexing job: support parallel download from MongoDB with two connections in
> Pipelined strategy
> ---
>
> Key: OAK-10778
> URL: https://issues.apache.org/jira/browse/OAK-10778
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Assignee: Nuno Santos
>Priority: Major
> Fix For: 1.64.0
>
>
> The current version of the Pipelined download strategy uses a single
> connection/thread to download from MongoDB. We can further increase the
> download speed by using an additional MongoDB connection. A Mongo deployment
> has 1 primary and 2 secondaries, so in principle we could have 1 connection
> to each secondary, effectively doubling the download speed.
> There are a few points to observe:
> - Connections should go to different secondaries. If both connections go to
> the same secondary, there's a high change that they will be limited by what a
> single replica can provide and of overloading that replica. So each secondary
> should have one and only one connection.
> - How to partition the range of documents to download between two threads.
> We are already downloading from Mongo in order of {{(_modified, _id)}}. A
> simple and effective partition strategy for 2 connections is for one to
> download in ascending and the other in descending order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (OAK-10778) Indexing job: support parallel download from MongoDB with two connections in Pipelined strategy
[
https://issues.apache.org/jira/browse/OAK-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reopened OAK-10778:
--
> Indexing job: support parallel download from MongoDB with two connections in
> Pipelined strategy
> ---
>
> Key: OAK-10778
> URL: https://issues.apache.org/jira/browse/OAK-10778
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Major
> Fix For: 1.64.0
>
>
> The current version of the Pipelined download strategy uses a single
> connection/thread to download from MongoDB. We can further increase the
> download speed by using an additional MongoDB connection. A Mongo deployment
> has 1 primary and 2 secondaries, so in principle we could have 1 connection
> to each secondary, effectively doubling the download speed.
> There are a few points to observe:
> - Connections should go to different secondaries. If both connections go to
> the same secondary, there's a high change that they will be limited by what a
> single replica can provide and of overloading that replica. So each secondary
> should have one and only one connection.
> - How to partition the range of documents to download between two threads.
> We are already downloading from Mongo in order of {{(_modified, _id)}}. A
> simple and effective partition strategy for 2 connections is for one to
> download in ascending and the other in descending order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10778) Indexing job: support parallel download from MongoDB with two connections in Pipelined strategy
[
https://issues.apache.org/jira/browse/OAK-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846702#comment-17846702
]
Julian Reschke commented on OAK-10778:
--
The new test seems to *require* Mongo to be present. That breaks a few
assumptions in CI and release management. We usually skip these type of tests
when a MongoDB instance is not available.
> Indexing job: support parallel download from MongoDB with two connections in
> Pipelined strategy
> ---
>
> Key: OAK-10778
> URL: https://issues.apache.org/jira/browse/OAK-10778
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Assignee: Nuno Santos
>Priority: Major
> Fix For: 1.64.0
>
>
> The current version of the Pipelined download strategy uses a single
> connection/thread to download from MongoDB. We can further increase the
> download speed by using an additional MongoDB connection. A Mongo deployment
> has 1 primary and 2 secondaries, so in principle we could have 1 connection
> to each secondary, effectively doubling the download speed.
> There are a few points to observe:
> - Connections should go to different secondaries. If both connections go to
> the same secondary, there's a high change that they will be limited by what a
> single replica can provide and of overloading that replica. So each secondary
> should have one and only one connection.
> - How to partition the range of documents to download between two threads.
> We are already downloading from Mongo in order of {{(_modified, _id)}}. A
> simple and effective partition strategy for 2 connections is for one to
> download in ascending and the other in descending order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10805) Build Jackrabbit/jackrabbit-oak-trunk #1472 failed
[ https://issues.apache.org/jira/browse/OAK-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846691#comment-17846691 ] Hudson commented on OAK-10805: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1474|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1474/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1474/console] > Build Jackrabbit/jackrabbit-oak-trunk #1472 failed > -- > > Key: OAK-10805 > URL: https://issues.apache.org/jira/browse/OAK-10805 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1472 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1472|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10807) Improve FileStoreBuilder to accept URIs for remote repositories
Andrei Dulceanu created OAK-10807:
-
Summary: Improve FileStoreBuilder to accept URIs for remote
repositories
Key: OAK-10807
URL: https://issues.apache.org/jira/browse/OAK-10807
Project: Jackrabbit Oak
Issue Type: Story
Reporter: Andrei Dulceanu
Assignee: Andrei Dulceanu
Currently {{FileStoreBuilder}} accepts only {{File}} path arguments in its
constructor making it impossible to use for {{oak-run}} tooling for remote
repositories. It should accept {{{}URI{}}}s as well, creating by default Azure
persistence backends.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10791) Build Jackrabbit/jackrabbit-oak-trunk-java17 #18 failed
[ https://issues.apache.org/jira/browse/OAK-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846613#comment-17846613 ] Hudson commented on OAK-10791: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk-java17 #20|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-java17/20/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-java17/20/console] > Build Jackrabbit/jackrabbit-oak-trunk-java17 #18 failed > --- > > Key: OAK-10791 > URL: https://issues.apache.org/jira/browse/OAK-10791 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk-java17 #18 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk-java17 > #18|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-java17/18/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-java17/18/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10805) Build Jackrabbit/jackrabbit-oak-trunk #1472 failed
[ https://issues.apache.org/jira/browse/OAK-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846601#comment-17846601 ] Hudson commented on OAK-10805: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1473|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1473/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1473/console] > Build Jackrabbit/jackrabbit-oak-trunk #1472 failed > -- > > Key: OAK-10805 > URL: https://issues.apache.org/jira/browse/OAK-10805 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1472 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1472|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10806) Expose Elastic indexes active status in OakIndexStats
Nitin Gupta created OAK-10806: - Summary: Expose Elastic indexes active status in OakIndexStats Key: OAK-10806 URL: https://issues.apache.org/jira/browse/OAK-10806 Project: Jackrabbit Oak Issue Type: Improvement Reporter: Nitin Gupta ES indexes are currently present in the OakIndexStats but they are all shown as active. We should make sure only the latest version of the ES indexes are shown as active. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10788) Indexing job downloader: shutdown gracefully all threads in case of failure
[ https://issues.apache.org/jira/browse/OAK-10788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nuno Santos resolved OAK-10788. --- Fix Version/s: 1.64.0 Resolution: Done > Indexing job downloader: shutdown gracefully all threads in case of failure > --- > > Key: OAK-10788 > URL: https://issues.apache.org/jira/browse/OAK-10788 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Nuno Santos >Priority: Minor > Fix For: 1.64.0 > > > If the download fails, the threads created by the Pipeline strategy are not > all being correctly shutdown, some of them may be left behind. As they are > all daemon threads, they will not prevent the JVM from shutting down. But > when they are forcibly closed at the JVM shutdown, they print in the logs > several exceptions (connections closed abruptly, trying to access objects > that were already closed) that are confusing and distract from the root cause > of the problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10800) DictionaryCompoundWordTokenFilter not supported in Elastic
[ https://issues.apache.org/jira/browse/OAK-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Fortino resolved OAK-10800. Fix Version/s: 1.64.0 Resolution: Fixed > DictionaryCompoundWordTokenFilter not supported in Elastic > -- > > Key: OAK-10800 > URL: https://issues.apache.org/jira/browse/OAK-10800 > Project: Jackrabbit Oak > Issue Type: Bug > Components: indexing >Reporter: Fabrizio Fortino >Assignee: Fabrizio Fortino >Priority: Minor > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10805) Build Jackrabbit/jackrabbit-oak-trunk #1472 failed
Hudson created OAK-10805: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1472 failed Key: OAK-10805 URL: https://issues.apache.org/jira/browse/OAK-10805 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1472 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1472|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1472/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10804) Indexing job: optimize check for hidden nodes
[
https://issues.apache.org/jira/browse/OAK-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Santos updated OAK-10804:
--
Description:
While downloading the repository from Mongo, the indexing job has to discard
hidden entries. This is being done by a call to
{{{}NodeStateUtils.isHiddenPath(){}}}. This call is rather expensive, as it
creates an iterator over the path segments, which requires creating a new
string for each path segment. As the indexing job has to check every entry to
verify if it is hidden, this creates a significant overhead.
The implementation of checking for hidden paths can be replaced by a simple
search for {{"/:"}} in the string representing the path, which requires no
object allocation and should therefore be much faster.
was:
While downloading the repository from Mongo, the indexing job has to discard
hidden entries. This is being done by a call to
`NodeStateUtils.isHiddenPath()`. This call is rather expensive, as it creates
an iterator over the path segments, which requires creating a new string for
each path segment. As the indexing job has to check every entry to verify if it
is hidden, this creates a significant overhead.
The implementation of checking for hidden paths can be replaced by a simple
search for {{"/:"}} in the string representing the path, which requires no
object allocation and should therefore be much faster.
> Indexing job: optimize check for hidden nodes
> -
>
> Key: OAK-10804
> URL: https://issues.apache.org/jira/browse/OAK-10804
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
>
> While downloading the repository from Mongo, the indexing job has to discard
> hidden entries. This is being done by a call to
> {{{}NodeStateUtils.isHiddenPath(){}}}. This call is rather expensive, as it
> creates an iterator over the path segments, which requires creating a new
> string for each path segment. As the indexing job has to check every entry to
> verify if it is hidden, this creates a significant overhead.
> The implementation of checking for hidden paths can be replaced by a simple
> search for {{"/:"}} in the string representing the path, which requires no
> object allocation and should therefore be much faster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-10804) Indexing job: optimize check for hidden nodes
[
https://issues.apache.org/jira/browse/OAK-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Santos updated OAK-10804:
--
Summary: Indexing job: optimize check for hidden nodes (was: Indexing job:
optimize check for if a node is hidden)
> Indexing job: optimize check for hidden nodes
> -
>
> Key: OAK-10804
> URL: https://issues.apache.org/jira/browse/OAK-10804
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
>Reporter: Nuno Santos
>Priority: Minor
>
> While downloading the repository from Mongo, the indexing job has to discard
> hidden entries. This is being done by a call to
> `NodeStateUtils.isHiddenPath()`. This call is rather expensive, as it creates
> an iterator over the path segments, which requires creating a new string for
> each path segment. As the indexing job has to check every entry to verify if
> it is hidden, this creates a significant overhead.
> The implementation of checking for hidden paths can be replaced by a simple
> search for {{"/:"}} in the string representing the path, which requires no
> object allocation and should therefore be much faster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OAK-10804) Indexing job: optimize check for if a node is hidden
Nuno Santos created OAK-10804:
-
Summary: Indexing job: optimize check for if a node is hidden
Key: OAK-10804
URL: https://issues.apache.org/jira/browse/OAK-10804
Project: Jackrabbit Oak
Issue Type: Improvement
Components: indexing
Reporter: Nuno Santos
While downloading the repository from Mongo, the indexing job has to discard
hidden entries. This is being done by a call to
`NodeStateUtils.isHiddenPath()`. This call is rather expensive, as it creates
an iterator over the path segments, which requires creating a new string for
each path segment. As the indexing job has to check every entry to verify if it
is hidden, this creates a significant overhead.
The implementation of checking for hidden paths can be replaced by a simple
search for {{"/:"}} in the string representing the path, which requires no
object allocation and should therefore be much faster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-10802) Build Jackrabbit/jackrabbit-oak-trunk #1469 failed
[ https://issues.apache.org/jira/browse/OAK-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846389#comment-17846389 ] Hudson commented on OAK-10802: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1471|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1471/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1471/console] > Build Jackrabbit/jackrabbit-oak-trunk #1469 failed > -- > > Key: OAK-10802 > URL: https://issues.apache.org/jira/browse/OAK-10802 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1469 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1469|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10739) Provide Support for Full Garbage Collection in Mongo Document Store
[ https://issues.apache.org/jira/browse/OAK-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846348#comment-17846348 ] Stefan Egli commented on OAK-10739: --- Yes it is for now only implemented for MongoDB. The largest part is outside of DocumentStore though, so adding RDB support is a relatively small effort (compared to the actual feature) > Provide Support for Full Garbage Collection in Mongo Document Store > --- > > Key: OAK-10739 > URL: https://issues.apache.org/jira/browse/OAK-10739 > Project: Jackrabbit Oak > Issue Type: Epic >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > Labels: DetailedGC > > We need to provide the support to collect & remove the full garbage for > DocumentNodeStore. > At the time of creating this epic garbage includes orphaned nodes, deleted > properties, unmerged branch commits, and old revisions. > > This list can be updated in case a new type of garbage is found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10739) Provide Support for Full Garbage Collection in Mongo Document Store
[ https://issues.apache.org/jira/browse/OAK-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846344#comment-17846344 ] Julian Reschke commented on OAK-10739: -- It would be good to clarify whether this is specific to MongoDocumentStore (if it is, what would need to be implemented in the RDBDocumentStore to support this?). > Provide Support for Full Garbage Collection in Mongo Document Store > --- > > Key: OAK-10739 > URL: https://issues.apache.org/jira/browse/OAK-10739 > Project: Jackrabbit Oak > Issue Type: Epic >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > Labels: DetailedGC > > We need to provide the support to collect & remove the full garbage for > DocumentNodeStore. > At the time of creating this epic garbage includes orphaned nodes, deleted > properties, unmerged branch commits, and old revisions. > > This list can be updated in case a new type of garbage is found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10792) Rename DetailedGC to FullGC
[ https://issues.apache.org/jira/browse/OAK-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846330#comment-17846330 ] Stefan Egli commented on OAK-10792: --- Also added https://github.com/apache/jackrabbit-oak/pull/1458 > Rename DetailedGC to FullGC > --- > > Key: OAK-10792 > URL: https://issues.apache.org/jira/browse/OAK-10792 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Daniel Iancu >Assignee: Rishabh Daim >Priority: Minor > Labels: DetailedGC > > Switching to FullGC instead of DetailedGC everywhere, method names, > constants, arguments etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10803) Compress in-memory property values
Daniel Iancu created OAK-10803: -- Summary: Compress in-memory property values Key: OAK-10803 URL: https://issues.apache.org/jira/browse/OAK-10803 Project: Jackrabbit Oak Issue Type: Improvement Components: core Reporter: Daniel Iancu Some properties in the repository can be quite large and consume a considerable amount of memory. E.g. large multi-valued properties, blob IDs that contain an inlined binary. With a certain size of the value, it may be beneficial to compress it when loaded into memory/cache and uncompress it only on access. This shouldn't be too difficult and can be implemented in a backward compatible way, because it only affects the in-memory representation and not how data is stored. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846290#comment-17846290 ] Julian Reschke commented on OAK-10786: -- trunk: [28f411a3ac|https://github.com/apache/jackrabbit-oak/commit/28f411a3acfcecc171dca06c25203f13ecdf29f8] [ecfe8f6381|https://github.com/apache/jackrabbit-oak/commit/ecfe8f63811ce256959ccb972e2b54b986721411] > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10786. -- Resolution: Fixed > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786 ] Julian Reschke deleted comment on OAK-10786: -- was (Author: reschke): trunk: [ecfe8f6381|https://github.com/apache/jackrabbit-oak/commit/ecfe8f63811ce256959ccb972e2b54b986721411] > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OAK-10792) Rename DetailedGC to FullGC
[ https://issues.apache.org/jira/browse/OAK-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim reopened OAK-10792: > Rename DetailedGC to FullGC > --- > > Key: OAK-10792 > URL: https://issues.apache.org/jira/browse/OAK-10792 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Daniel Iancu >Assignee: Rishabh Daim >Priority: Minor > Labels: DetailedGC > > Switching to FullGC instead of DetailedGC everywhere, method names, > constants, arguments etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10739) Provide Support for Full Garbage Collection in Mongo Document Store
[ https://issues.apache.org/jira/browse/OAK-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846265#comment-17846265 ] Stefan Egli commented on OAK-10739: --- The PR for merging the main feature branch to trunk has just been created at https://github.com/apache/jackrabbit-oak/pull/1454 > Provide Support for Full Garbage Collection in Mongo Document Store > --- > > Key: OAK-10739 > URL: https://issues.apache.org/jira/browse/OAK-10739 > Project: Jackrabbit Oak > Issue Type: Epic >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > Labels: DetailedGC > > We need to provide the support to collect & remove the full garbage for > DocumentNodeStore. > At the time of creating this epic garbage includes orphaned nodes, deleted > properties, unmerged branch commits, and old revisions. > > This list can be updated in case a new type of garbage is found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10739) Provide Support for Full Garbage Collection in Mongo Document Store
[ https://issues.apache.org/jira/browse/OAK-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim updated OAK-10739: --- Summary: Provide Support for Full Garbage Collection in Mongo Document Store (was: Provide Support for Full Garbage Collection in Document Node Store) > Provide Support for Full Garbage Collection in Mongo Document Store > --- > > Key: OAK-10739 > URL: https://issues.apache.org/jira/browse/OAK-10739 > Project: Jackrabbit Oak > Issue Type: Epic >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > Labels: DetailedGC > > We need to provide the support to collect & remove the full garbage for > DocumentNodeStore. > At the time of creating this epic garbage includes orphaned nodes, deleted > properties, unmerged branch commits, and old revisions. > > This list can be updated in case a new type of garbage is found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10765) Fetch only id while checking for GAP orphan during verification
[ https://issues.apache.org/jira/browse/OAK-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim resolved OAK-10765. Resolution: Fixed > Fetch only id while checking for GAP orphan during verification > --- > > Key: OAK-10765 > URL: https://issues.apache.org/jira/browse/OAK-10765 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > > Currently, we are fetching the complete document while checking whether it > exists or not during GAP orphan verification. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10792) Rename DetailedGC to FullGC
[ https://issues.apache.org/jira/browse/OAK-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846260#comment-17846260 ] Rishabh Daim commented on OAK-10792: [PR|https://github.com/apache/jackrabbit-oak/pull/1440] merged, closing the ticket. > Rename DetailedGC to FullGC > --- > > Key: OAK-10792 > URL: https://issues.apache.org/jira/browse/OAK-10792 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Daniel Iancu >Assignee: Rishabh Daim >Priority: Minor > Labels: DetailedGC > > Switching to FullGC instead of DetailedGC everywhere, method names, > constants, arguments etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10792) Rename DetailedGC to FullGC
[ https://issues.apache.org/jira/browse/OAK-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim resolved OAK-10792. Resolution: Fixed > Rename DetailedGC to FullGC > --- > > Key: OAK-10792 > URL: https://issues.apache.org/jira/browse/OAK-10792 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Daniel Iancu >Assignee: Rishabh Daim >Priority: Minor > Labels: DetailedGC > > Switching to FullGC instead of DetailedGC everywhere, method names, > constants, arguments etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10792) Rename DetailedGC to FullGC
[ https://issues.apache.org/jira/browse/OAK-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim reassigned OAK-10792: -- Assignee: Rishabh Daim > Rename DetailedGC to FullGC > --- > > Key: OAK-10792 > URL: https://issues.apache.org/jira/browse/OAK-10792 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Daniel Iancu >Assignee: Rishabh Daim >Priority: Minor > Labels: DetailedGC > > Switching to FullGC instead of DetailedGC everywhere, method names, > constants, arguments etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10802) Build Jackrabbit/jackrabbit-oak-trunk #1469 failed
[ https://issues.apache.org/jira/browse/OAK-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846252#comment-17846252 ] Hudson commented on OAK-10802: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1470|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1470/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1470/console] > Build Jackrabbit/jackrabbit-oak-trunk #1469 failed > -- > > Key: OAK-10802 > URL: https://issues.apache.org/jira/browse/OAK-10802 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1469 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1469|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846217#comment-17846217 ] Julian Reschke commented on OAK-10786: -- Re-opening because the RAT license header checks fail for the automaton package. As we can't *change* the license, and the license did not change in in the Lucene project either, I'm proposing to add these files to the RAT exclude list. > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-6756) Convert oak-auth-external to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846216#comment-17846216 ] Angela Schreiber commented on OAK-6756: --- [~baedke], sounds like a plan i was on vacation but will try to make time to look at the PR this week. > Convert oak-auth-external to OSGi R7 annotations > > > Key: OAK-6756 > URL: https://issues.apache.org/jira/browse/OAK-6756 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-external >Reporter: Robert Munteanu >Assignee: Manfred Baedke >Priority: Major > Labels: technical_debt > Fix For: 1.64.0 > > Attachments: cschneider-OAK-6756.osgi-diff.txt > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reopened OAK-10786: -- > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10802) Build Jackrabbit/jackrabbit-oak-trunk #1469 failed
Hudson created OAK-10802: Summary: Build Jackrabbit/jackrabbit-oak-trunk #1469 failed Key: OAK-10802 URL: https://issues.apache.org/jira/browse/OAK-10802 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit/jackrabbit-oak-trunk #1469 has failed. First failed run: [Jackrabbit/jackrabbit-oak-trunk #1469|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1469/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10799) Update (shaded) Guava to 33.2.0
[ https://issues.apache.org/jira/browse/OAK-10799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846181#comment-17846181 ] Julian Reschke commented on OAK-10799: -- trunk: [bc73ca3107|https://github.com/apache/jackrabbit-oak/commit/bc73ca3107021d2d0f2eb6d9b96046486389646f] > Update (shaded) Guava to 33.2.0 > --- > > Key: OAK-10799 > URL: https://issues.apache.org/jira/browse/OAK-10799 > Project: Jackrabbit Oak > Issue Type: Task > Components: shaded-guava >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10799) Update (shaded) Guava to 33.2.0
[ https://issues.apache.org/jira/browse/OAK-10799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-10799. -- Fix Version/s: 1.64.0 Resolution: Fixed > Update (shaded) Guava to 33.2.0 > --- > > Key: OAK-10799 > URL: https://issues.apache.org/jira/browse/OAK-10799 > Project: Jackrabbit Oak > Issue Type: Task > Components: shaded-guava >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10786) oak-lucene: use copy of lucene-core 4.7.2 source code
[ https://issues.apache.org/jira/browse/OAK-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846176#comment-17846176 ] Julian Reschke commented on OAK-10786: -- trunk: [ecfe8f6381|https://github.com/apache/jackrabbit-oak/commit/ecfe8f63811ce256959ccb972e2b54b986721411] > oak-lucene: use copy of lucene-core 4.7.2 source code > - > > Key: OAK-10786 > URL: https://issues.apache.org/jira/browse/OAK-10786 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.64.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
