[
https://issues.apache.org/jira/browse/OAK-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152461#comment-16152461
]
Robert Munteanu commented on OAK-6578:
--------------------------------------
[~chetanm] - good catch, that's the indexed value, not the path.
Given your comment on OAK-5173, would it make sense to keep the new
{{queryEntries}} method in the {{IndexStoreStrategy}} interface or should I try
to keep it in the unique store implementation?
> 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)
