[
https://issues.apache.org/jira/browse/OAK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088713#comment-17088713
]
Amrit Verma commented on OAK-8934:
----------------------------------
[~thomasm] Since it was not a direct backport (some files didn't exist) I did
the backport manually and committed changes locally.
Then I used the following command -
{code:java}
git diff -w -p HEAD~1 {code}
which is mentioned here -
[https://jackrabbit.apache.org/oak/docs/developing-with-git.html]
I don't know why it didn't produce correct patch this time.
> Indexing: filter entries with a regular expression
> --------------------------------------------------
>
> Key: OAK-8934
> URL: https://issues.apache.org/jira/browse/OAK-8934
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
> Labels: amrit
> Fix For: 1.26.0
>
> Attachments: OAK-8934-1_8.patch, OAK-8934-1_8_svn.patch
>
>
> We should provide a way to filter the index using a regular expression. For
> example, only index nodes that contain a reference to another node. (Not a
> JCR reference, but a reference within the value itself). For example, index a
> node if one of the properties contains:
> * /content/abc
> * <html...> <a href="/content/abc">
> * and so on
> This will allow to run a query to find if /content/abc is referenced. The
> index and the query will probably need to use a tag, and the cost of the
> index needs to be high. Otherwise the query engine can't know when this index
> should be used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
