[
https://issues.apache.org/jira/browse/OAK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469331#comment-17469331
]
Roy Teeuwen commented on OAK-8971:
----------------------------------
Just tested it on our DEV environment, and I think indeed that filtering on
client side would be a lot easier, I tried the SQL like query, and that took 22
seconds to execute, without the like it took 6,5 seconds.
If I use my extra indexed field from the IndexFieldProvider it takes 2 seconds,
so that one does still stay the fastest one though! Looking forward to the docs
for the valueRegex to see if we can speed up those 6,5 seconds so that I can
remove the deprecated IndexFieldProvider :)
{code:java}
SELECT [jcr:path] from [nt:base]
WHERE native('lucene','inlinevariable:(company)')
AND isdescendantnode('/content/my-site/en'){code}
> 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)
