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
Describe the bug The GET /search filter-lang parameter doesn't default to cql2-text, like it is defined in the specification of the filter extension. Instead, cql2-json is used as the default when no value is supplied. https://github.com/stac-api-extensions/filter?tab=readme-ov-file#get-query-parameters-and-post-json-fields
https://github.com/stac-utils/stac-fastapi-elasticsearch/blob/main/stac_fastapi/elasticsearch/stac_fastapi/elasticsearch/core.py#L383-L388
To Reproduce Steps to reproduce the behavior:
Expected behavior The default filter-lang in a GET search is cql2-text and queries can be parsed successfully.
The text was updated successfully, but these errors were encountered:
stac-utils#179: filter extension - set filter-lang=cql2-text as defau…
4e4b5eb
…lt for GET search
Merge branch 'main' into stac-utils#179
c38ce2b
Merge pull request #180 from StijnCaerts/#179
0cad96c
Set correct default filter-lang for GET /search requests
No branches or pull requests
Describe the bug
The GET /search filter-lang parameter doesn't default to cql2-text, like it is defined in the specification of the filter extension. Instead, cql2-json is used as the default when no value is supplied.
https://github.com/stac-api-extensions/filter?tab=readme-ov-file#get-query-parameters-and-post-json-fields
https://github.com/stac-utils/stac-fastapi-elasticsearch/blob/main/stac_fastapi/elasticsearch/stac_fastapi/elasticsearch/core.py#L383-L388
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The default filter-lang in a GET search is cql2-text and queries can be parsed successfully.
The text was updated successfully, but these errors were encountered: