Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Smiley, David W." <dsmiley@mitre.org>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Date: Fri, 21 May 2010 10:21:59 -0400
Subject: Re: Wildcard queries
Thread-Topic: Wildcard queries
Thread-Index: Acr48PmpMLSpBhmuTk648h0EWrVb9w==
Message-ID: <2D51B7CC-2987-41C2-939D-EA0086660B1A@mitre.org>
References: <4BF6949F.4090201@zib.de>
In-Reply-To: <4BF6949F.4090201@zib.de>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I absolutely consider this a bug too.  Cast your vote:
https://issues.apache.org/jira/browse/SOLR-219

~ David

On May 21, 2010, at 10:11 AM, Sascha Szott wrote:

> Hi folks,
>=20
> what's the idea behind the fact that no text analysis (e.g. lowercasing)=
=20
> is performed on wildcarded search terms?
>=20
> In my context this behaviour seems to be counter-intuitive (I guess=20
> that's the case in the majority of applications) and my application=20
> needs to lowercase any input term before sending the HTTP request to my=20
> Solr server.
>=20
> Would it be easy to disable this behaviour in Solr (1.5)? I would like=20
> to see a config parameter (per field type) that allows to disable this=20
> "odd" behaviour if needed. To ensure backward compatibility the "odd"=20
> behaviour should be the default anymore.
>=20
> Am I missing any drawbacks?
>=20
> Best,
> Sascha
>=20