Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problems with range searches for time with lte #2731

Closed
CGenie opened this issue Mar 5, 2013 · 2 comments
Closed

Problems with range searches for time with lte #2731

CGenie opened this issue Mar 5, 2013 · 2 comments
Labels
>bug v0.20.6 v0.90.0.RC1

Comments

@CGenie
Copy link

CGenie commented Mar 5, 2013

Hello,

I cannot find this issue as reported, but I'm having problems with range queries over fields of date type with 'lte' enabled. Full gist reproducing the problem, as well as some analysis by clintongormley can be found here: https://gist.github.com/anonymous/4482696
For now I can live with 'lt' query which seems to work fine, but this is either an evident bug or I'm misusing the date field.

NOTE: My ElasticSearch version is 0.20.5.

Przemek
@kimchy
Copy link
Member

kimchy commented Mar 6, 2013

As clinton noted, our parsing when doing range filters can be better implemented to support "just" hours. Easily fixed...

@kimchy kimchy closed this as completed in e1409a9 Mar 6, 2013
kimchy added a commit that referenced this issue Mar 6, 2013
@kimchy
Problems with range searches for time with lte
17858ea 
fixes #2731
@CGenie
Copy link
Author

CGenie commented Mar 6, 2013

Thanks! That was quick ;)

@imotov imotov mentioned this issue Dec 15, 2013
Closed
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
Problems with range searches for time with lte
fb10cc6 
fixes elastic#2731
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.20.6 v0.90.0.RC1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @CGenie