[
https://issues.apache.org/jira/browse/SOLR-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1025:
-------------------------------
Fix Version/s: 1.4
Can you give a concrete example (actual query strings) of what isn't working?
> QParsers ignore configured defaultType's
> ----------------------------------------
>
> Key: SOLR-1025
> URL: https://issues.apache.org/jira/browse/SOLR-1025
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Environment: All platforms
> Reporter: Rick Moynihan
> Fix For: 1.4
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Whilst trying to implement my own QParser that would work with any XML
> configured default query type, I noticed that the BoostQParserPlugin had a
> hard coded assumption that means it ignores the defaultType specified in the
> XML.
> The problem appears to be the following line:
> baseParser = subQuery(localParams.get(QueryParsing.V), null);
> Passing null into subQuery, appears to cause it to get an
> OldLuceneQParserPlugin if there is no defaultType specified as a localParam,
> i.e. it doesn't appear to look further down the chain to inspect whether a
> defaultType has been set in solrconfig.xml.
> Other QParsers appear to make similar assumptions (though I haven't tested
> them). Changing the above code to the following should resolve the issue.
> I'd suggest that this functionality should also be made available inside the
> QParser base class, so all QParsers can correctly resolve the defaultType.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
