[ https://issues.apache.org/jira/browse/SOLR-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323804#comment-17323804 ]
Erik Hatcher commented on SOLR-15345: ------------------------------------- +1 on `fq.defType` There definitely shouldn't be a single query parser setting that affects q and also fq - they are entirely differently purposes where `q` ought to be assumed to be literally a user entered query and the rest of the parser configuration can be controlled with other parameters, with a fixed, predictable way to nail `fq`'s down concretely. > filter queries (fq) ignore the default query parser (defType) > ------------------------------------------------------------- > > Key: SOLR-15345 > URL: https://issues.apache.org/jira/browse/SOLR-15345 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Dawid Weiss > Priority: Major > > This would be a breaking change but is a good puzzler - if you're using a > non-standard query parser (set up as default everywhere), filter queries > completely ignore it. One can override locally via > {code}fq={!type=...}...{code} but it seems like an obscure solution. > See this code in QueryComponent: > https://github.com/apache/solr/blob/b8b65ce5060e71ebca1f8acc16559ada41e5df77/solr/core/src/java/org/apache/solr/handler/component/QueryComponent.java#L160 > and for fq: > https://github.com/apache/solr/blob/b8b65ce5060e71ebca1f8acc16559ada41e5df77/solr/core/src/java/org/apache/solr/handler/component/QueryComponent.java#L210 > Is this behavior intended? -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org