[ https://issues.apache.org/jira/browse/SOLR-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895680#action_12895680 ]
Karl Wright commented on SOLR-2031: ----------------------------------- The reason is that I may be (will be) using the same search component in two different contexts within the SAME request. So the request handler override is not going to help. See SOLR-2026 for a high-level description of why I need to do this. ;-) > QueryComponent's default query parser should be configurable from > solrconfig.xml > -------------------------------------------------------------------------------- > > Key: SOLR-2031 > URL: https://issues.apache.org/jira/browse/SOLR-2031 > Project: Solr > Issue Type: Improvement > Components: SearchComponents - other > Reporter: Karl Wright > Priority: Minor > Attachments: SOLR-2031.patch > > > In a multi-lucene-query environment, QueryComponent's way of selecting a > default query parser must include solrconfig.xml support to be useful. It > can't just get the default query parser from the request arguments. -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org