[
https://issues.apache.org/jira/browse/OAK-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029317#comment-15029317
]
Vikas Saurabh edited comment on OAK-3686 at 12/1/15 3:34 PM:
-------------------------------------------------------------
[~teofili], I'm attaching a [patch|^OAK-3686.patch]. Current implementation
uses unique=true for path cursor while a similar issue for lucene - OAK-2754
(Use non unique PathCursor in LucenePropertyIndex) was done for lucene property
index to use non unique path cursor. I'm not sure if we can do it safely for
solr or not (i.e. the current version of solr queries would be returning unique
nodes anyway for relevant cases)
was (Author: catholicon):
@teofili, I'm attaching a [patch|^OAK-3686.patch]. Current implementation uses
unique=true for path cursor while a similar issue for lucene - OAK-2754 (Use
non unique PathCursor in LucenePropertyIndex) was done for lucene property
index to use non unique path cursor. I'm not sure if we can do it safely for
solr or not (i.e. the current version of solr queries would be returning unique
nodes anyway for relevant cases)
> Solr suggestion results should have 1 row per suggestion with appropriate
> column names
> --------------------------------------------------------------------------------------
>
> Key: OAK-3686
> URL: https://issues.apache.org/jira/browse/OAK-3686
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: solr
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.3.12
>
> Attachments: OAK-3686.patch
>
>
> Currently suggest query returns just one row with {{rep:suggest()}} column
> containing a string that needs to be parsed.
> It'd better if each suggestion is returned as individual row with column
> names such as {{suggestion}}, {{weight}}(???), etc.
> (This is essentially the same issue as OAK-3509 but for solr)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
