[
https://issues.apache.org/jira/browse/OAK-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469756#comment-17469756
]
Amrit Verma commented on OAK-8971:
----------------------------------
[~royteeuwen] [~thomasm] Yes valueRegex should work for this case. It will
affect the complete index though. If we add "valueRegex=%%" to the
{{oak:QueryIndexDefinition}} node (i.e. the index node), that index would only
contain those properties whose values contain {{%%}} so, {{"Hello, welcome to
%%company%%"}} would be indexed but {{"Hello, welcome to company"}} would not
be indexed. So this should serve the purpose of filtering.
During query, we still need to search by {{contains(s.*, 'company')}} and then
use {{like}} or client side filtering as suggested above.
> 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)
