f373020349
Previously, if YEAR() was used as and ORDER BY argument without being wrapped with another scalar (e.g. YEAR(birth_date) + 10), no script ordering was used but instead the underlying field (e.g. birth_date) was used instead as a performance optimisation. This works correctly if YEAR() is the only ORDER BY arg but if further args are used as tie breakers for the ordering wrong results are produced. This is because 2 rows with the different birth_date but on the same year are not tied as the underlying ordering is on birth_date and not on the YEAR(birth_date), and the following ORDER BY args are ignored. Remove this optimisation for YEAR() to avoid incorrect results in such cases. As a consequence another bug is revealed: scalar functions on top of nested fields produce scripted sorting/filtering which is not yet supported. In such cases no error was thrown but instead all values for such nested fields were null and were passed to the script implementing the sorting/filtering, producing incorrect results. Detect such cases and throw a validation exception. Fixes: #51224 (cherry picked from commit f41efd6753dc3650a7eabb3e07b02b3b32c5704c) |
||
|---|---|---|
| .. | ||
| appendix | ||
| endpoints | ||
| functions | ||
| language | ||
| concepts.asciidoc | ||
| getting-started.asciidoc | ||
| index.asciidoc | ||
| limitations.asciidoc | ||
| overview.asciidoc | ||
| security.asciidoc | ||