-
Notifications
You must be signed in to change notification settings - Fork 76
Make faceting on booleans return True and False instead of "T" and "F" #72
Comments
This is probably a problem in pyes. EU doesn't do any conversions. We could investigate this in pyes or just wait until after we switch to pyelasticsearch. |
To be clear, the "T" and "F" are present when doing raw queries against ES, so it is not that pyes and/or EU are doing something wrong, but that they aren't doing anything. |
I think this is a problem with ElasticSearch and I'm not really sure why it's doing what it's doing. If you use curl to hit ES, it returns this:
So the I don't think there's anything we can do here because EU can't distinguish between whether |
I thought about fixing this in pull #147, but didn't because in my research I bumped into this bug in Elasticsearch: I think I'm inclined to not fix this in ElasticUtils. I'm going to close this out. |
Consider an index with a boolean value 'happy'.
Notice that
term
is"T"
or"F"
. It would make a lot more sense for it to beTrue
orFalse
, considering this is a boolean field. This is because, for some reason, ElasticSearch does it this way. When interacting with this field it gives back the proper jsontrue
andfalse
, but in facets it does not.Can we smooth over this oddity?
The text was updated successfully, but these errors were encountered: