From b56c38dadfde1a69e0087f57b44ec1f19cb1b8f2 Mon Sep 17 00:00:00 2001 From: Andrei Stefan Date: Mon, 27 Aug 2018 18:49:16 +0300 Subject: [PATCH] * Added breaking change section for GROUP BY behavior: now it considers null or empty values as a separate group/bucket. Previously, they were ignored. * This is part of backporting of https://github.com/elastic/elasticsearch/pull/32832 --- docs/reference/migration/migrate_6_5.asciidoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/reference/migration/migrate_6_5.asciidoc b/docs/reference/migration/migrate_6_5.asciidoc index 913d9567cb850..a6b22cf38d356 100644 --- a/docs/reference/migration/migrate_6_5.asciidoc +++ b/docs/reference/migration/migrate_6_5.asciidoc @@ -5,6 +5,7 @@ This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 6.5. * <> +* <> See also <> and <>. @@ -23,3 +24,13 @@ Elasticsearch will log a warning on startup and log with the new pattern. It will not change the logging configuration files though. You should make this change before 7.0 because in 7.0 Elasticsearch will no longer automatically add the node name to the logging configuration if it isn't already present. + +[[breaking_65_sql_changes]] +=== SQL plugin changes + +==== Grouping by columns with missing values will create an additional group + +An additional group will be present in the result of requests containing a +`GROUP BY` for a column that has missing values in the returned documents. +The records with missing values in the grouped by column will be collectively +considered a single bucket.