[ https://issues.apache.org/jira/browse/SOLR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851637#comment-13851637 ]
Furkan KAMACI commented on SOLR-218: ------------------------------------ [~markrmil...@gmail.com] This is an old issue and SolrQueryParser has changed since that time. There is an effort for leading wildcard at comments of current issue but {SOLR-1321:https://issues.apache.org/jira/browse/SOLR-1321} has resolved the problem as like described here: http://lucene.472066.n3.nabble.com/hi-allowLeadingWildcard-is-it-possible-or-not-yet-td495457.html Is there anything to do for this issue? if not issue can be closed, if yes I can help and create a patch for it. > 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: 4.6 > > > 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 was sent by Atlassian JIRA (v6.1.4#6159) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org