We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
[ ] elastic.v7 (for Elasticsearch 7.x) [x] elastic.v6 (for Elasticsearch 6.x) [ ] elastic.v5 (for Elasticsearch 5.x) [ ] elastic.v3 (for Elasticsearch 2.x) [ ] elastic.v2 (for Elasticsearch 1.x)
Package should produce range query with gt, gte, lt, lte etc. fields
gt
gte
lt
lte
Package produces range query with from, to, etc.
from
to
A comment from elasticsearch repo mentioning that this was already deprecated in 0.90.4 elastic/elasticsearch#48538 (comment)
0.90.4
and a related issue from 2016 #196
Create a range query with lower limit .Gte() or upper limit .Lte() and observe the produced source.
.Gte()
.Lte()
The text was updated successfully, but these errors were encountered:
Duplicate of #1187.
While it might be deprecated, it doesn't log a deprecation warning and is still alive and kicking, even in 7.5.
Sorry, something went wrong.
No branches or pull requests
Which version of Elastic are you using?
[ ] elastic.v7 (for Elasticsearch 7.x)
[x] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
Package should produce range query with
gt
,gte
,lt
,lte
etc. fieldsPlease describe the actual behavior
Package produces range query with
from
,to
, etc.A comment from elasticsearch repo mentioning that this was already deprecated in
0.90.4
elastic/elasticsearch#48538 (comment)
and a related issue from 2016
#196
Any steps to reproduce the behavior?
Create a range query with lower limit
.Gte()
or upper limit.Lte()
and observe the produced source.The text was updated successfully, but these errors were encountered: