[
https://issues.apache.org/jira/browse/OAK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470507#comment-17470507
]
Thomas Mueller commented on OAK-8971:
-------------------------------------
> It is indeed very weird that the query takes so long
Well if the query returns 172'000 entries than yes it can take long... But by
default the query should break (throw an exception) after reading 100'000
entries, so I assume you have configured a higher limit. I would recommend to
not read more than a few hundred entries per query. For reports (that might
take a long time to execute) it might be better to use keyset pagination --
https://jackrabbit.apache.org/oak/docs/query/query-engine.html#Keyset_Pagination
valueRegex: in theory we could backport it... but I'm not sure we should, as
normally we don't backport new features.
> 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)
