Raven server indexes booleans upper-case, but the client queries them lower-case

[Lars Corneliussen]

When indexing boolean fields, "Terms" lists "False" and "False", but the client api generates field:true or field:false when using Query with expressions.
Workarround is to store boolean fields Analyzed - but that doesn't make to much sense...

Using build 701; is this fixed in never versions?

[Oren Eini (Ayende Rahien)]

Are you using a custom index?

[Lars Corneliussen]

Yes.

AddMap<Xyz>(
                fs => from h in fs
                      select new Result
                             {
                                 Bool = h.Transactions.Any()
                             });

var load = s.Query<Index.Result, Index>()
                    .Where(d => !d.Bool)
                    .AsProjection<Index.Result>();

_
Lars

[Oren Eini (Ayende Rahien)]

This is strange, can you show the full index def?

[Lars Corneliussen]

Was about to write a huge mail with lots of code, but when trying to prove the problem, the Terms suddenly showed "false" and "true", instead of "False" and "True".

Some more testing showed that this depends on if the field is set as analyzed or not. Analyzed -> lower-case, Not Analyzed -> upper case

But IMHO boolean fields should be indexed unanalyzed, as i do not want to find things with "t" or tr"... But I might be wrong.

Still want the code?

_

Lars

[Oren Eini (Ayende Rahien)]

No, if this is the case, than that is by design.

There is a difference between how we index things in the different modes.

For boolean fields, you are better off sticking with the Default, instead of messing with it.

[Oren Eini (Ayende Rahien)]

Are you using a custom index?

On Saturday, June 9, 2012, Lars Corneliussen wrote: