You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Trejkaz (JIRA)" <ji...@apache.org> on 2008/03/27 00:49:29 UTC
[jira] Updated: (LUCENE-1245) MultiFieldQueryParser is not friendly
for overriding getFieldQuery(String,String,int)
[ https://issues.apache.org/jira/browse/LUCENE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trejkaz updated LUCENE-1245:
----------------------------
Lucene Fields: [New, Patch Available] (was: [New])
Summary: MultiFieldQueryParser is not friendly for overriding getFieldQuery(String,String,int) (was: MultiFieldQueryParser is not friendly for overriding)
(Updating title to be more specific about what wasn't friendly.)
> MultiFieldQueryParser is not friendly for overriding getFieldQuery(String,String,int)
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-1245
> URL: https://issues.apache.org/jira/browse/LUCENE-1245
> Project: Lucene - Java
> Issue Type: Improvement
> Components: QueryParser
> Affects Versions: 2.3.2
> Reporter: Trejkaz
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org