lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-218) Support for Lucene QueryParser properties via solrconfig.xml file
Date Mon, 20 Apr 2009 14:27:47 GMT

    [ https://issues.apache.org/jira/browse/SOLR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700802#action_12700802
] 

Mark Miller commented on SOLR-218:
----------------------------------

I made the same changes, but I was using trunk. I'll give it a shot with 1.3 in a bit and
report back.

> Support for Lucene QueryParser properties via solrconfig.xml file
> -----------------------------------------------------------------
>
>                 Key: SOLR-218
>                 URL: https://issues.apache.org/jira/browse/SOLR-218
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.1.0
>            Reporter: Michael Pelz-Sherman
>             Fix For: 1.5
>
>
> The SolrQueryParser class, which extends Lucene's QueryParser class, does not provide
any way of setting the various QueryParser properties via the solr config file (solrconfig.xml).
These properties include:
> allowLeadingWildcard (Set to true to allow * and ? as the first character of a PrefixQuery
and WildcardQuery)
> dateResolution: Sets the default date resolution used by RangeQueries for fields for
which no specific date resolutions has been set.
> defaultOperator: Sets the boolean operator of the QueryParser.
> fuzzyMinSim: Set the minimum similarity for fuzzy queries.
> locale: Set locale used by date range parsing.
> lowercaseExpandedTerms: Whether terms of wildcard, prefix, fuzzy and range queries are
to be automatically lower-cased or not.
> phraseSlop: Sets the default slop for phrases.
> useOldRangeQuery: By default QueryParser uses new ConstantScoreRangeQuery in preference
to RangeQuery for range queries.
> This can be achieved by calling the setter methods for these properties in the SolrQueryParser
constructor,
>   public SolrQueryParser(IndexSchema schema, String defaultField) {
>     super(defaultField == null ? schema.getDefaultSearchFieldName() : defaultField, schema.getQueryAnalyzer());
>     this.schema = schema;
>     setAllowLeadingWildcard(SolrConfig.config.getBool("query/setAllowLeadingWildcard"));
>     setLowercaseExpandedTerms(SolrConfig.config.getBool("query/lowerCaseExpandedTerms"));
>   }
> In addition, solr should not modify these values from the defaults provided by Lucene,
as it currently does by calling setLowercaseExpandedTerms(false) in this method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message