[
https://issues.apache.org/jira/browse/SOLR-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533926#comment-13533926
]
Vlado Kurelec commented on SOLR-3925:
-------------------------------------
Hi, at first, thanks a lot for this patch.
I've built it on a rev. 1406758 and found following issues:
- edismax query throws an exception when there's no sf parameter
- SpanFirst doesn't process the search term through the query anayzer defined
on that field
- if search term is enclosed in (), they are not striped but passed as part of
the term
How come it is not included in night build? Is there another way to do boost by
position?
> Expose SpanFirst in eDismax
> ---------------------------
>
> Key: SOLR-3925
> URL: https://issues.apache.org/jira/browse/SOLR-3925
> Project: Solr
> Issue Type: Improvement
> Components: query parsers
> Affects Versions: 4.0-BETA
> Environment: solr-spec 5.0.0.2012.10.09.19.29.59
> solr-impl 5.0-SNAPSHOT 1366361:1396116M - markus - 2012-10-09 19:29:59
> Reporter: Markus Jelsma
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-3925-trunk-1.patch, SOLR-3925-trunk-2.patch
>
>
> Expose Lucene's SpanFirst capability in Solr's extended Dismax query parser.
> This issue adds the SF-parameter (SpanFirst) and takes a FIELD~DISTANCE^BOOST
> formatted value.
> For example, sf=title~5^2 will give a boost of 2 if one of the normal
> clauses, originally generated for automatic phrase queries, is located within
> five positions from the field's start.
> Unit test is included and all tests pass.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
