[
https://issues.apache.org/jira/browse/SOLR-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157350#comment-13157350
]
Yonik Seeley commented on SOLR-1982:
------------------------------------
I ran onto this myself while looking at the query parser code again. We
introspect all of the schema field types every time a query parser is created -
really not ideal for performance. Perhaps this should be cached in the schema,
or at
Zero length prefix queries have pretty much always been allowed in solr, and
leading wildcard queries have been effectively allowed with the default example
schema since '09. Seems like when we get around to fixing this stuff,
permissive should be the default, but should somehow be overridable (or maybe
we can punt to a higher level parser like edismax to handle per-field
overrides).
> Leading wildcard queries work for "all" fields if
> ReversedWildcardFilterFactory is used for "any" field
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-1982
> URL: https://issues.apache.org/jira/browse/SOLR-1982
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4, 1.4.1
> Reporter: Hoss Man
>
> As noted on the mailing list...
> http://search.lucidimagination.com/search/document/8064e6877f49e4c4/leading_wildcard_query_strangeness
> ...SolrQueryParse supports leading wild card queries for *any* field as long
> as at least one field type exists in the schema.xml which uses
> ReversedWildcardFilterFactory -- even if that field type is never used.
> This is extremely confusing, and ost likely indicates a bug in how
> SolrQueryParser deals with ReversedWildcardFilterFactory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
