[
https://issues.apache.org/jira/browse/OAK-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152457#comment-16152457
]
Chetan Mehrotra commented on OAK-6578:
--------------------------------------
Approach looks fine to me. We can use this to properly solve OAK-5173 but that
would require flattening the multiple paths reported per index entry. Would be
good if that can also be supported i.e. ensuring that one hit may produce
multiple index entry
{noformat}
+ private interface HitProducer<T> {
+ T produce(NodeState indexHit, String pathName);
+ }
{noformat}
Here {{pathName}} as parameter name is misleading and confusing as its indexed
value .... right?
> Enhance the IndexStoreStrategy to return list of matching values and paths
> --------------------------------------------------------------------------
>
> Key: OAK-6578
> URL: https://issues.apache.org/jira/browse/OAK-6578
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: 1.8, 1.7.7
>
> Attachments: OAK-6578.patch
>
>
> For OAK-6506 I would need to extract from each index a list of all property
> values and paths. The property values would be used to check for duplicates,
> while the paths will be used for reporting.
> As the IndexStoreStrategy interface and its implementations do not support
> such access, we need to provide it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
