[
https://issues.apache.org/jira/browse/OAK-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163156#comment-16163156
]
Vikas Saurabh commented on OAK-6656:
------------------------------------
Added ignored test at [r1808128|https://svn.apache.org/r1808128].
[~chetanm], while a very simple fix is add {{ordered}} to
{{MissingIndexProviderStrategy#ignore}} set. While that works as intended but
the log message isn't descriptive enough - basically there's no information
about which definition is being complained about. Inside the provider we do
have definition NodeState which we can log - that can be 'hint' enough to find
which index is being talked about. But, I was wondering if we can somehow get
the path information there. Any ideas?
> OrderedPropertyIndexEditorProvider does not return Editor to IndexUpdate
> leading to "ordered" being marked as missing type
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: OAK-6656
> URL: https://issues.apache.org/jira/browse/OAK-6656
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.7.7, 1.4.18, 1.6.5
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4, candidate_oak_1_6
> Fix For: 1.8
>
>
> OAK-3768 removed support for {{ordered}} property index but the intention of
> the removal was that presence of ordered index should only log a WARN every
> now and then (10k times on invocation of EditorProvider).
> But, it returns {{null}} editor which is takes as there is no provider of
> ordered index. Which, in turn, as the config be, can fail commits (or async
> indexing if index was async).
> We should handle this gracefully.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
