: In the default schema.xml, only text_rev fieldType has
: ReversedWildcardFilterFactory. The query below (manu_exact:*in) returns
: two documents (whose manu_exact is Belkin).
:
: Am i missing something?
:
:
http://localhost:8983/solr/select/?q=manu_exact%3A*in&version=2.2&start=0&rows=10&in
> that's how SolrQueryParser works at the moment, yes.
In the default schema.xml, only text_rev fieldType has
ReversedWildcardFilterFactory. The query below (manu_exact:*in) returns two
documents (whose manu_exact is Belkin).
Am i missing something?
http://localhost:8983/solr/select/?q=manu_e
: Does this mean leading * operator can only be used with fields whose
: fieldType definition has ReversedWildcardFilterFactory at index time?
that's how SolrQueryParser works at the moment, yes.
-Hoss
> that's not correct what SolrQueryParser does is
> check which field
> types use ReversedWildcardFilterFactory at indexing time,
> and then when
> parsing queries, it allows fields that use field types to
> be parsed with a leading wildcard.
Does this mean leading * operator can only be u
: > I'm going to guess that is what you meant, that the very
: > presence of the
: > filter in the schema, whether it is used or not, allows you
: > to do wildcard
: > searches.
:
: Exactly.
that's not correct what SolrQueryParser does is check which field
types use ReversedWildcardFilterFa
> I'm going to guess that is what you meant, that the very
> presence of the
> filter in the schema, whether it is used or not, allows you
> to do wildcard
> searches.
Exactly.
> Is that documented anywhere and I just missed it? I'm
> sure it is.
I knew it from source code of SolrQueryParser.
p
--
View this message in context:
http://lucene.472066.n3.nabble.com/Leading-Wildcard-query-strangeness-tp931809p933600.html
Sent from the Solr - User mailing list archive at Nabble.com.
> We've got an app in production that executes leading
> wildcard queries just
> fine.
>
>
> 0
> 1298
>
> title:*news
>
>
>
>
> The same app in dev/qa has undergone a major
> schema/solrconfig overhaul,
> including introducing multiple cores, and leading wildcard
> queries no lon
ssfully executing Wildcard queries. Is there another way without
QueryParser.setAllowLeadingWildcard(true)?
(Running 1.4 in all environments, although "newer" versions of 1.4
(downloaded more recently) in dev and qa.)
Thoughts?
--
View this message in context:
http://lucene.
