[ https://issues.apache.org/jira/browse/OAK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088770#comment-17088770 ]
Julian Reschke edited comment on OAK-8934 at 4/21/20, 3:27 PM: --------------------------------------------------------------- FWIW, if a patch can't be applied because branches differ too much, it might be better to look at why they are different and maybe backport the in-between changes as well. was (Author: reschke): FWIW, if a patch can't be applies because branches differ too much, it might be better to look at why they are different and maybe backport the in-between changes as well. > 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)