[
https://issues.apache.org/jira/browse/OAK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467175#comment-17467175
]
Roy Teeuwen commented on OAK-8971:
----------------------------------
[~thomasm] I see that the IndexFieldProvider is deprecated. The use case that
you implemented with the dynamicBoost is totally not the use case we use it for
though.
We have for example the following text saved in a property "Hello, welcome to
%%company%%". In the IndexFieldProvider we will scrape every property and if
there is a property that is delimited with %%, we will save that as a separate
lucene property.
That way we can do a native query where we say, give every node that has
"%%company%%" in it (or other words than company of course). Is there an
alternative to IndexFieldProvider to do this? The %% delimiters get stripped
out by the analyzers in the default lucene index so we can't search for
%%company%%, and also the default lucene index is even deprecated nowadays to
use
> 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)
