Querystring not being analyzed

Elastic Stack Elasticsearch
4

I think you will not bother anybody when you share your problems. That is
what user mail list if for :slight_smile:
You can always clone fresh ES code into new directory and run gradlew. This
will build fresh ES instance ready for your tests.

Regards,
Lukas

On Wed, Feb 24, 2010 at 4:22 AM, Robert Eanes reanes@gmail.com wrote:

Thanks for responding so quickly. I'd love to test it out, but I'm
having trouble building the latest version from github. This is
almost certainly due to my very limited java experience, rather than
an actual problem with the code. For instance I'd never heard of
gradle until today. In any case, I don't want to bother you with
that, just knowing it's fixed for an upcoming release is great for
me. Thanks again!

On Feb 23, 3:16 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

Yep, this is a bug in how I handle this case in the enhanced query
parser
in elasticsearch. I have already pushed a fixed. Can you give it a go?

-shay.banon

On Tue, Feb 23, 2010 at 7:18 PM, Robert Eanes rea...@gmail.com wrote:

I'm trying to get a simple case-insensitive search to work by running
the querystring through the "standard" analyzer, but it doesn't seem
to be working for me. The index seems to be run through the analyzer,
as a querystring that is all lowercase matches a mixed-case record. A
mixed or uppercase querystring never matches though. I've tried
explicitly setting the analyzer parameter, with no effect.
I'm using 0.4.0, with no changes to the config file (which is empty).

Thanks for any help you can give me - here is an example session
illustrating the problem:

~ $ curl -XPUThttp://localhost:9200/twitter/tweet/1-d
'
{
user : "Kimchy",
postDate : "2009-11-15T14:12:12",
message : "trying out Elastic Search"
}
'
{"ok":true,"_index":"twitter","_type":"tweet","_id":"1"}

~ $ curl -XGET "http://localhost:9200/twitter/tweet/_search?
q=user:kimchy"
{"_shards":{"total":5,"successful":5,"failed":0},"hits":{"total":
1,"hits":[{"_index":"twitter","_type":"tweet","_id":"1", "_source" :
{
user : "Kimchy",
postDate : "2009-11-15T14:12:12",
message : "trying out Elastic Search"
}
}]}}

So far, so good. The lowercase term matched the mixed-case original,
but then:

~ $ curl -XGET "http://localhost:9200/twitter/tweet/_search?
q=user:KIMCHY"
{"_shards":{"total":5,"successful":5,"failed":0},"hits":{"total":
0,"hits":}}

With explicit analyzer specified:

~ $ curl -XGET "http://localhost:9200/twitter/tweet/_search?
q=user:KIMCHY&analyzer=standard"
{"_shards":{"total":5,"successful":5,"failed":0},"hits":{"total":
0,"hits":}}