[GitHub] [spark] arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate

2019-05-08 Thread GitBox
arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate URL: https://github.com/apache/spark/pull/22696#issuecomment-490530838 Indeed. The following query fails in Postgresql: `select id from (select 1 as id) t having id > 0` `ERROR:

[GitHub] [spark] arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate

2019-05-08 Thread GitBox
arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate URL: https://github.com/apache/spark/pull/22696#issuecomment-490531403 Weird, the 2 previous comments are actually in the Future...

[GitHub] [spark] arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate

2019-05-08 Thread GitBox
arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate URL: https://github.com/apache/spark/pull/22696#issuecomment-490529740 Indeed. Postgresql fails with `ERROR: column "t.id" must appear in the GROUP BY clause or be used in an aggregate

[GitHub] [spark] arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate

2019-05-08 Thread GitBox
arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate URL: https://github.com/apache/spark/pull/22696#issuecomment-490472938 That sql is not valid in Oracle but this works as I described above: `select t.id from (select 5 as id from dual) t

[GitHub] [spark] arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate

2019-05-07 Thread GitBox
arkguil commented on issue #22696: [SPARK-25708][SQL] HAVING without GROUP BY means global aggregate URL: https://github.com/apache/spark/pull/22696#issuecomment-490184967 @cloud-fan / @gatorsmile , just stumbled on this while investigating an issue with a query while migrating to 2.4...