[ 
https://issues.apache.org/jira/browse/SOLR-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003073#comment-13003073
 ] 

David Smiley edited comment on SOLR-1982 at 3/6/11 12:19 AM:
-------------------------------------------------------------

It's true that the existing code path already supports a plain '\*'. What I 
meant to say was that in adding the code to throw an error when 
ReverseWildcardFilterFactory is not in the field and there is a leading 
wildcard, do still support a plain '\*' anyway. Sorry for any confusion.

      was (Author: dsmiley):
    It's true that the existing code path already supports a plain '*'. What I 
meant to say was that in adding the code to throw an error when 
ReverseWildcardFilterFactory is not in the field and there is a leading 
wildcard, do still support a plain '*' anyway. Sorry for any confusion.
  
> 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.
-
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]

Reply via email to