[
https://issues.apache.org/jira/browse/OAK-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015502#comment-15015502
]
Tommaso Teofili commented on OAK-3509:
--------------------------------------
bq. I'm just planning to support 2 columns (which can probably be extended
later as you hinted above) - rep:spellcheck and jcr:score (where I'm planning
to put value of weight of each suggestion as jcr:score). Does that sound fine?
+1
bq. Also, this is clearly a backward compatibility issue. I'm not sure how we
deal with that. Do we just document it? What our take usually about backporting
(to say 1.2 or 1.0) for such issues?
yes that's a non backward compatible change, I think we should keep in trunk
for 1.3+ releases and avoid backporting. We should document it on Oak Docs site
e.g. "...since Oak 1.3.x suggest results are provided in separate rows ... "
> 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.11
>
>
> 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)
