[
https://issues.apache.org/jira/browse/LUCENE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz closed LUCENE-1245.
---------------------------
Resolution: Not A Problem
I guess this resolution is correct. We have stopped using the basic query
parser and now use the flexible one precisely because of this sort of issue, so
the issue itself is no longer an issue for us.
> MultiFieldQueryParser is not friendly for overriding
> getFieldQuery(String,String,int)
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-1245
> URL: https://issues.apache.org/jira/browse/LUCENE-1245
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/queryparser
> Affects Versions: 2.3.2
> Reporter: Trejkaz
> Attachments: multifield.patch
>
>
> LUCENE-1213 fixed an issue in MultiFieldQueryParser where the slop parameter
> wasn't being properly applied. Problem is, the fix which eventually got
> committed is calling super.getFieldQuery(String,String), bypassing any
> possibility of customising the query behaviour.
> This should be relatively simply fixable by modifying
> getFieldQuery(String,String,int) to, if field is null, recursively call
> getFieldQuery(String,String,int) instead of setting the slop itself. This
> gives subclasses which override either getFieldQuery method a chance to do
> something different.
--
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
