Error on Discover tab for non-time based patterns with default sort by _score #6698
Assignees
Labels
Comments
|
Looks like this is the change elastic/elasticsearch#16573 |
|
I misspoke, the issue is actually with |
Bargs
pushed a commit
that referenced
this issue
Mar 31, 2016
Fixes #6698 - ES no longer supports unmapped_type param on _score field sorting
jbudz
added a commit
that referenced
this issue
Apr 18, 2023
EUI `77.0.0` ➡️ `77.1.1` ## [`77.1.0`](https://github.com/elastic/eui/tree/v77.1.0) - Updated `EuiDatePicker` to display a warning icon and correctly set `aria-invalid` when `isInvalid` is passed ([#6677](elastic/eui#6677)) - Updated `EuiFilePicker` to display an alert icon when `isInvalid` ([#6678](elastic/eui#6678)) - Updated `EuiTextArea` to display an alert icon when `isInvalid` ([#6679](elastic/eui#6679)) - Updated `EuiTextArea` to support the `isLoading` prop ([#6679](elastic/eui#6679)) - Updated `EuiComboBox` to display a warning icon and correctly set `aria-invalid` when `isInvalid` is passed ([#6680](elastic/eui#6680)) **Bug fixes** - Fixed `EuiAccordion` to not set an `aria-expanded` attribute on non-interactive `buttonElement`s ([#6694](elastic/eui#6694)) - Fixed an `EuiPopoverFooter` bug causing nested popovers within popovers (note: not a recommended use-case) to unintentionally override its panel padding size inherited from context ([#6698](elastic/eui#6698)) - Fixed `EuiComboBox` to only delete the last selected item on backspace if the input caret is present ([#6699](elastic/eui#6699)) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jon <jon@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I haven't tracked down the exact commit that caused it, but Elasticsearch has apparently removed the ability to include
unmapped_typein a sort on the_scorefield (maybe any meta field?).By default the Discover tab issues an msearch for non time based patterns with the following clause
"sort":[{"_score":{"order":"desc","unmapped_type":"boolean"}}]ES master is now returning an error with
[_score] failed to parse field [unmapped_type]. If you issue the same request withoutunmapped_type, it succeeds.Regular fields appear to still support
unmapped_type, which is why time based index patterns still work since they sort by the time field by default.I'd like to figure out if this was an intentional change in ES. If it was, we'll need to stop using
unmapped_typeon _score and maybe all meta fields.The text was updated successfully, but these errors were encountered: