[
https://issues.apache.org/jira/browse/OAK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965095#comment-14965095
]
Vikas Saurabh commented on OAK-3509:
------------------------------------
The null path/virtual row discussion most probably won't affect this
improvement. I'm a little busy at some other work. I'd try to prepare a patch
around this as soon I can get some time.
About virtual columns, I'm not sure if it's acceptable to rely on a particular
index type - but then, as a count argument, rep:suggest/spellcheck already rely
on index being used as lucene/solr based... so, we already have a precedent.
> Lucene suggestion results should have 1 row per suggestion with appropriate
> column names
> ----------------------------------------------------------------------------------------
>
> Key: OAK-3509
> URL: https://issues.apache.org/jira/browse/OAK-3509
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Tommaso Teofili
> Priority: Minor
> Fix For: 1.3.9
>
>
> 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.
> (cc [~teofili])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
