Skip to content

fix: fallback if term orderby is set to none #4104

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
Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

fix: fallback if term orderby is set to none #4104

wants to merge 1 commit into from

Conversation

@fabianmarz
Copy link
Contributor

Description of the Change

On my local setup at some point I came across a term query which has set the orderby argument set to none. This resulted in a ES exception since there was no field to order on. This PR addresses the fix similar to #3318

Todo

  • Add test

Changelog Entry

Fixed - Added fallback if term orderby is set to none

Checklist:
@felipeelia
Copy link
Member

Hi @fabianmarz, thanks for sending the PR! We are almost wrapping up all issues that will be included in the 5.2.0 release. Do you think you'll be able to work on this in the next week? Thanks!
@fabianmarz
Copy link
Contributor Author

Hey @felipeelia, I'll try to implement the test this week 👍
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@fabianmarz @felipeelia