[
https://issues.apache.org/jira/browse/OAK-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059575#comment-15059575
]
Chetan Mehrotra commented on OAK-3785:
--------------------------------------
Again like OAK-3576 bit late for review but still ;)
I checked the logic and was thinking that same effect can be achieved now also
by just setting {{index}} to false on the given property definition node. The
presence of property definition would trigger {{propertyChanged}} call for such
a property to lead to {{propertiesChanged}} set to true. And this would trigger
the call to {{makeDocument}} and that would enable call to the
{{IndexFieldProvider}}
Thoughts?
> IndexDefinition should expose underlying node state
> ---------------------------------------------------
>
> Key: OAK-3785
> URL: https://issues.apache.org/jira/browse/OAK-3785
> 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 pass index definition's {{NodeState}} to registered
> callbacks. Thus, we want to expose the underlying {{NodeState}} for currently
> used {{IndexDefinition}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
