[
https://issues.apache.org/jira/browse/OAK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470489#comment-17470489
]
Roy Teeuwen commented on OAK-8971:
----------------------------------
Super, thanks both for the clarifications and help! Sadly enough it seems I
wont be able to test this, I am using oak-core 1.22 (AEM 6.5.11), so only when
we would go to AEMaaCS we will be able to do the migration to use valueRegex
(it's also only then that we will have the issue of IndexFieldProvider being
deprecated so that's ok)
[~thomasm] for reference, the query that took 2 seconds on the custom field in
the lucene index is on a JCR repo where the following query returns 172106
paths:
{code:java}
SELECT [jcr:path] from [nt:base]
WHERE isdescendantnode('/content/my-site/en') {code}
It is indeed very weird that the query takes so long (query tested and time it
takes taken from CRX DE > Tools > Query JCR_SQL2), seeing as it's doing a
native query on a specific index field. If I use the Query Performance tool and
then I get following result, so I guess the time in CRX De is also the
rendering of the actual paths
{noformat}
Indexes Used
lucene(/oak:index/lucene)
Execution Time
Total time: 1126 ms
Query execution time: 0 ms
Get nodes time: 24 ms
Result node count time: 1102 ms
Number of nodes in result: 2165 {noformat}
> Indexing: dynamic boost, as an alternative to IndexFieldProvider
> ----------------------------------------------------------------
>
> Key: OAK-8971
> URL: https://issues.apache.org/jira/browse/OAK-8971
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
> Fix For: 1.30.0
>
> Attachments: OAK-8971.patch
>
>
> The org.apache.jackrabbit.oak.plugins.index.lucene.spi.IndexFieldProvider is
> a callback that allows to change the behavior of indexing. There are multiple
> problems:
> * (1) Not available using oak-run
> * (2) Only available for Lucene indexes
> Instead of a callback, a configuration option in the index property should be
> added, such that the most commonly used features are available in oak-run,
> and can be implemented in other indexes (e.g. Elastisearch, Solr).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
