Deprecated ticket #164
Assignees
Comments
widal001
changed the title
widal001
added this to the
Evaluation plan and tools established to organize learning milestone
widal001
removed this from the
1.1 Evaluation plan and tools established to organize learning milestone
widal001
changed the title
acouch
pushed a commit
that referenced
this issue
Sep 18, 2024
…vapbc#195) Fixes #164 Adds support to our search query builder layer to handle building queries for filtering on ints and dates between specific date ranges. Added ints and dates in the same ticket as the queries are essentially the same, just ints vs dates. While it throws an exception if both start and end values are None, I think the API request schema should also do that so that the error is more relevant/accurate to the API, but I can add that later (likely a lot more niche edge cases to handle for requests). Nothing too exciting with these queries, they work as expected and are just simple ranges. The test dataset is roughly accurate (turns out books didn't always have exact release dates until the last ~20 years). I also have tested these queries manually with the opportunity endpoints fields, the following two queries would work (can be tested locally at http://localhost:5601/app/dev_tools#/console ): ``` GET opportunity-index-alias/_search { "size": 5, "query": { "bool": { "filter": [ { "range": { "summary.post_date": { "gte": "2020-01-01", "lte": "2025-01-01" } } } ] } } } GET opportunity-index-alias/_search { "size": 12, "query": { "bool": { "filter": [ { "range": { "summary.award_floor": { "gte": 1234, "lte": 100000 } } } ] } } } ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The text was updated successfully, but these errors were encountered: