[jira] [Updated] (OAK-10813) Improve performance of Oak-mongo.js function to remove/list nodes
[ https://issues.apache.org/jira/browse/OAK-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10813: - Component/s: run > 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 > Components: run >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Major > Fix For: 1.64.0 > > > 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] [Resolved] (OAK-10813) Improve performance of Oak-mongo.js function to remove/list nodes
[ https://issues.apache.org/jira/browse/OAK-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim resolved OAK-10813. Fix Version/s: 1.64.0 Resolution: Fixed > 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 >Priority: Major > Fix For: 1.64.0 > > > 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-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=17848312#comment-17848312 ] Hudson commented on OAK-10817: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures #9|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/9/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/9/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] [Updated] (OAK-10624) o.a.j.o.namepath.JcrPathParser does not accept some valid local names containing "{" or "}".
[
https://issues.apache.org/jira/browse/OAK-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated OAK-10624:
-
Fix Version/s: 1.66.0
(was: 1.64.0)
> o.a.j.o.namepath.JcrPathParser does not accept some valid local names
> containing "{" or "}".
>
>
> Key: OAK-10624
> URL: https://issues.apache.org/jira/browse/OAK-10624
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core-spi
>Reporter: Manfred Baedke
>Assignee: Manfred Baedke
>Priority: Major
> Fix For: 1.66.0
>
>
> See PathParserTest#testCurlyBracketsInNames()
> Some valid paths not accepted:
> {code:java}
> "{a", "{a[1]", "/{/a", "/{[1]/a", "{", "{[1]", "/{", "/{[1]", "/}", "/}[1]",
> "/a:}", "/a:}[1]"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OAK-6772) Convert oak-solr-core to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6772: Fix Version/s: 1.66.0 (was: 1.64.0) > Convert oak-solr-core to OSGi R7 annotations > > > Key: OAK-6772 > URL: https://issues.apache.org/jira/browse/OAK-6772 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: solr >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-6762) Convert oak-blob to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6762: Fix Version/s: 1.66.0 (was: 1.64.0) > Convert oak-blob to OSGi R7 annotations > --- > > Key: OAK-6762 > URL: https://issues.apache.org/jira/browse/OAK-6762 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob >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-10621) o.a.j.o.namepath.JcrPathParser does not accept indexed expanded names.
[ https://issues.apache.org/jira/browse/OAK-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10621: - Fix Version/s: 1.66.0 (was: 1.64.0) > o.a.j.o.namepath.JcrPathParser does not accept indexed expanded names. > -- > > Key: OAK-10621 > URL: https://issues.apache.org/jira/browse/OAK-10621 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core-spi >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.66.0 > > > Instead it gives an error: "']' not allowed in name." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-6773) Convert oak-store-composite to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6773: Fix Version/s: 1.66.0 (was: 1.64.0) > Convert oak-store-composite to OSGi R7 annotations > -- > > Key: OAK-6773 > URL: https://issues.apache.org/jira/browse/OAK-6773 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: composite >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-6766) Convert oak-lucene to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6766: Fix Version/s: 1.66.0 (was: 1.64.0) > Convert oak-lucene to OSGi R7 annotations > - > > Key: OAK-6766 > URL: https://issues.apache.org/jira/browse/OAK-6766 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: lucene >Reporter: Robert Munteanu >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.66.0 > > Attachments: LuceneIndexProvider-ConfigUI-new.png, > LuceneIndexProvider-ConfigUI-old.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-6761) Convert oak-blob-plugins to OSGi R7 annotations
[ https://issues.apache.org/jira/browse/OAK-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6761: Fix Version/s: 1.66.0 (was: 1.64.0) > Convert oak-blob-plugins to OSGi R7 annotations > --- > > Key: OAK-6761 > URL: https://issues.apache.org/jira/browse/OAK-6761 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: blob-plugins >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-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6741: Fix Version/s: 1.66.0 (was: 1.64.0) > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu >Assignee: Manfred Baedke >Priority: Major > Fix For: 1.66.0 > > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R7 annotations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated OAK-6756: Fix Version/s: 1.66.0 (was: 1.64.0) > 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.66.0 > > Attachments: cschneider-OAK-6756.osgi-diff.txt > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10824) Release Oak 1.64.0
Julian Reschke created OAK-10824: Summary: Release Oak 1.64.0 Key: OAK-10824 URL: https://issues.apache.org/jira/browse/OAK-10824 Project: Jackrabbit Oak Issue Type: Task Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10823) Support Oak-mongo.js remove functions with mongosh shell
Rishabh Daim created OAK-10823:
--
Summary: Support Oak-mongo.js remove functions with mongosh shell
Key: OAK-10823
URL: https://issues.apache.org/jira/browse/OAK-10823
Project: Jackrabbit Oak
Issue Type: Improvement
Reporter: Rishabh Daim
Assignee: Rishabh Daim
Functions to remove nodes in the oak-mongo.js file don't work with the
*mongosh* shell.
Reason: we are using *db.collection.remove()* to delete nodes which return *
{ acknowledged: true, deletedCount: 0 }
* for _*mongosh*_ and *WriteResult(\{ "nRemoved" : 0 })* for _*mongo*_ shell.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OAK-8046) Result items are not always correctly counted against the configured read limit if a query uses a lucene index
[ https://issues.apache.org/jira/browse/OAK-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848198#comment-17848198 ] Roy Teeuwen commented on OAK-8046: -- [~thomasm] Thanks for the prompt reply! Seeing as we have more than 100.000 nodes / pages and we have processes which query for these pages, we are getting this log all the time. So I guess the only thing we can do is move this class to an ignored log file :(? Very weird to get this as LOG.info but we can't act / do anything about it > Result items are not always correctly counted against the configured read > limit if a query uses a lucene index > --- > > Key: OAK-8046 > URL: https://issues.apache.org/jira/browse/OAK-8046 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Affects Versions: 1.8.7 >Reporter: Georg Henzler >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.12.0, 1.10.1, 1.8.12 > > Attachments: OAK-8046-take2.patch, OAK-8046.patch > > > There are cases where an index is re-opened during query execution. In that > case, already returned entries are read again and skipped, so basically > counted twice. This should be fixed to only count entries once (see also [1]) > The issue most likely exists since the read limit was introduced with OAK-6875 > [1] > https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-8046) Result items are not always correctly counted against the configured read limit if a query uses a lucene index
[ https://issues.apache.org/jira/browse/OAK-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848193#comment-17848193 ] Thomas Mueller commented on OAK-8046: - > Should a reindex be triggered No. That won't help. > Result items are not always correctly counted against the configured read > limit if a query uses a lucene index > --- > > Key: OAK-8046 > URL: https://issues.apache.org/jira/browse/OAK-8046 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Affects Versions: 1.8.7 >Reporter: Georg Henzler >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.12.0, 1.10.1, 1.8.12 > > Attachments: OAK-8046-take2.patch, OAK-8046.patch > > > There are cases where an index is re-opened during query execution. In that > case, already returned entries are read again and skipped, so basically > counted twice. This should be fixed to only count entries once (see also [1]) > The issue most likely exists since the read limit was introduced with OAK-6875 > [1] > https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-8046) Result items are not always correctly counted against the configured read limit if a query uses a lucene index
[ https://issues.apache.org/jira/browse/OAK-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848192#comment-17848192 ] Thomas Mueller commented on OAK-8046: - [~royteeuwen] it means while the query is still running (and reading more nodes), the index was updated concurrently. Indexes are updated every ~5 seconds. Best is if the queries read less than 200 nodes, and relatively quickly (within a second or so). If you have queries that read 100'000 or more nodes, it is quite easy to get into this situation. With less than 200 nodes, it's typically never a problem. (There's also the case where less than 200 nodes are read, but very slowly... but that's unlikely). > Result items are not always correctly counted against the configured read > limit if a query uses a lucene index > --- > > Key: OAK-8046 > URL: https://issues.apache.org/jira/browse/OAK-8046 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Affects Versions: 1.8.7 >Reporter: Georg Henzler >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.12.0, 1.10.1, 1.8.12 > > Attachments: OAK-8046-take2.patch, OAK-8046.patch > > > There are cases where an index is re-opened during query execution. In that > case, already returned entries are read again and skipped, so basically > counted twice. This should be fixed to only count entries once (see also [1]) > The issue most likely exists since the read limit was introduced with OAK-6875 > [1] > https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-8046) Result items are not always correctly counted against the configured read limit if a query uses a lucene index
[ https://issues.apache.org/jira/browse/OAK-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848177#comment-17848177 ] Roy Teeuwen commented on OAK-8046: -- [~thomasm] [~catholicon] we see the "Change in index version detected. Query would be performed without offset" logged 100.00 times per day on certain instances, but for me it's not clear what the action is required to fix this? Can we as consumer of Apache Oak (used in AEM) do anything to mitigate this log line of occurring? Should a reindex be triggered, or something else? > Result items are not always correctly counted against the configured read > limit if a query uses a lucene index > --- > > Key: OAK-8046 > URL: https://issues.apache.org/jira/browse/OAK-8046 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Affects Versions: 1.8.7 >Reporter: Georg Henzler >Assignee: Vikas Saurabh >Priority: Major > Fix For: 1.12.0, 1.10.1, 1.8.12 > > Attachments: OAK-8046-take2.patch, OAK-8046.patch > > > There are cases where an index is re-opened during query execution. In that > case, already returned entries are read again and skipped, so basically > counted twice. This should be fixed to only count entries once (see also [1]) > The issue most likely exists since the read limit was introduced with OAK-6875 > [1] > https://lists.apache.org/thread.html/dddf9834fee0bccb6e48f61ba2a01430e34fc0b464b12809f7dfe2eb@%3Coak-dev.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OAK-10822) Build Jackrabbit/jackrabbit-oak-trunk #1487 failed
[ https://issues.apache.org/jira/browse/OAK-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848165#comment-17848165 ] Hudson commented on OAK-10822: -- Build is still failing. Failed run: [Jackrabbit/jackrabbit-oak-trunk #1488|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1488/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1488/console] > 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 >Priority: Major > > 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=17848125#comment-17848125 ] Hudson commented on OAK-10817: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk-nsfixtures #8|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/8/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk-nsfixtures/8/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-10711) remove use of Guava Preconditions.checkNotNull()
[ https://issues.apache.org/jira/browse/OAK-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848104#comment-17848104 ] julian.reschke commented on OAK-10711: -- Afaict, another option is just to remove it. New Java versions create good diagnostics for NPEs automatically... Am 21.05.2024 10:30 schrieb "Rishabh Daim (Jira)" : [ https://issues.apache.org/jira/browse/OAK-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim reassigned OAK-10711: -- Assignee: Rishabh Daim -- This message was sent by Atlassian Jira (v8.20.10#820010) > remove use of Guava Preconditions.checkNotNull() > > > Key: OAK-10711 > URL: https://issues.apache.org/jira/browse/OAK-10711 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Minor > > Can be replaced by JDK Objects.requireNotNull(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10711) remove use of Guava Preconditions.checkNotNull()
[ https://issues.apache.org/jira/browse/OAK-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishabh Daim reassigned OAK-10711: -- Assignee: Rishabh Daim > remove use of Guava Preconditions.checkNotNull() > > > Key: OAK-10711 > URL: https://issues.apache.org/jira/browse/OAK-10711 > Project: Jackrabbit Oak > Issue Type: Technical task >Reporter: Rishabh Daim >Assignee: Rishabh Daim >Priority: Minor > > Can be replaced by JDK Objects.requireNotNull(). -- 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)
