[jira] [Created] (OAK-10831) Look at incorporating the following gists in Oak Run
Patrique Legault created OAK-10831: -- Summary: Look at incorporating the following gists in Oak Run Key: OAK-10831 URL: https://issues.apache.org/jira/browse/OAK-10831 Project: Jackrabbit Oak Issue Type: Improvement Components: oak-run Reporter: Patrique Legault The following scripts are used to help fix inconsistencies in the repository [1] / [2]. To help streamline and manage a consistency repository check these should be included in oak-run as a groovy script. This will prevent dependencies on third party scripts and allow for proper management of the scripts [1] [https://gist.githubusercontent.com/stillalex/e7067bcb86c89bef66c8/raw/d7a5a9b839c3bb0ae5840252022f871fd38374d3/childCount.groovy] [2] [https://gist.githubusercontent.com/stillalex/43c49af065e3dd1fd5bf/raw/9e726a59f75b46e7b474f7ac763b0888d5a3f0c3/rmNode.groovy] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-10648) Null Props Cause Incorrect Query Estimation
Patrique Legault created OAK-10648: -- Summary: Null Props Cause Incorrect Query Estimation Key: OAK-10648 URL: https://issues.apache.org/jira/browse/OAK-10648 Project: Jackrabbit Oak Issue Type: Bug Components: indexing Reporter: Patrique Legault Attachments: Non Union Query Plan.json, Non Union With Null Check.json, Screenshot 2024-02-13 at 9.30.43 AM.png, Union Query Plan.json, cqTagLucene.json Using null props in a query can cause the query engine to incorrectly estimate the cost of query plan which can lead to a traversal and slow queries to execute. If you look at the query plan below the number of null props documents is quiet high yet the cost for the query is only 19. When we execute the UNION query the cost is 38 which is why it is not selected when in reality the original cost should be much higher. After removing the null check the cost estimation is drastically different and correctly reflects the number of documents in the index. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OAK-9815) Add Path to the Node in the logs in order to better debug
Patrique Legault created OAK-9815: - Summary: Add Path to the Node in the logs in order to better debug Key: OAK-9815 URL: https://issues.apache.org/jira/browse/OAK-9815 Project: Jackrabbit Oak Issue Type: Improvement Components: core Reporter: Patrique Legault When debugging issues related to Oak it would be nice to see the path that was attempted to be operated in order to understand where the Oak error started from. Can we include the Node Path in the logs that caused the IllegalArgumentException *https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/core/MutableTree.java#L351* -- This message was sent by Atlassian Jira (v8.20.7#820007)
