[
https://issues.apache.org/jira/browse/OAK-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059946#comment-15059946
]
Vikas Saurabh commented on OAK-3789:
------------------------------------
Reverted in [r1720344|http://svn.apache.org/r1720344]
[r1720259|http://svn.apache.org/r1720259].
bq. same effect can be achieved now also by just setting {{index}}
Setting {{index}} to false has more side-effects that we intend. What we want
is to avoid any field generation by default implementation. {{index}}=false,
otoh, would impact index selection etc as well.
I think we should use (and hence not add fields in other methods too) -
{{indexAggregatedNode}}, {{addTypedOrderedFields}}, property index loop in
{{makeDocument}} etc.
Would do these changes and upload patch.
> Index definition for properties should allow "not creating any fields" for
> that property
> ----------------------------------------------------------------------------------------
>
> Key: OAK-3789
> URL: https://issues.apache.org/jira/browse/OAK-3789
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.3.13
>
>
> For OAK-3576, we want to have index definitions for properties which are
> relevant *only* for a registered callback. Such properties, when changes,
> shouldn't create any fields. All other indexing behavior (while indexing or
> while creating query plans etc) should remain the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
