-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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.
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
Add support for querying on range fields in query_string and simple_query_string queries #26555
Comments
i would like to pick this up as my first PR, do i have to assign this to myself to start working on it ? |
@arunagar You can just open a PR and we can then work on get your change in. No one from Elastic is working on this yet as it hasn't been assigned yet. |
This is solved tangentially by #26552 because the |
I will start on this and send a PR, i may take some time to get accustomed to the code, but i will work on this. |
Hey i was looking at the query_string test for range, there is already existing test in here for range elasticsearch/core/src/test/java/org/elasticsearch/index/query/QueryStringQueryBuilderTests.java Line 918 in c709b8d
Is the intention to write a unit test with query_string, which makes sure that the relation is intersect ? |
@arunagar this test is on a keyword field, what's missing is a query on a range field: |
@jimczi Is there any problem if I work on the needed test? |
Range fields are in a separate module, so rather than adding a test to QueryStringQueryBuilderTests I'm going to create a new AbstractQueryTestCase extension in mapper-extras. Does that make sense @jpountz ? |
[TEST] Add test for *_range fields in query_string queries Closes #26555
Currently querying on range fields via
query_string
andsimple_query_string
queries results in an error indicating that we do not support this. Whereas querying these fields via therange
queries just works as expected.Adding support for this is trivial. One caveat is that there is no way to specify the
relation
(like inrange
query). Therefor if range fields are queries viaquery_string
andsimple_query_string
then we should default tointersects
relation.The text was updated successfully, but these errors were encountered: