The 100 100 is the sole matching row for the join condition, so it
would be right result,
NULLNULLNULL40
NULLNULL12 35
NULLNULL48 NULL
NULL40 NULLNULL
12 35 NULLNULL
48 NULLNULLNULL
100 100 100 100
It's fixe
well. i had some free time to search it. from here:
http://www.postgresql.org/docs/9.3/static/sql-select.html#SQL-UNION you'll
see the default is indeed UNION DISTINCT. so changing it to UNION ALL
you'll get different results - are they the ones you're expecting?
On Wed, Mar 12, 2014 at 9:36 AM
interesting.don't know the answer but could you change the UNION in the
Postgres to UNION ALL? I'd be curious if the default is UNION DISTINCT on
that platform. That would at least partially explain postgres behaviour
leaving hive the odd man out.
On Wed, Mar 12, 2014 at 6:47 AM, Martin Kud
Hi all,
I've tried BigTop test for join_filters:
CREATE TABLE myinput1(key int, value int);
LOAD DATA LOCAL INPATH 'seed_data_files/in3.txt' INTO TABLE myinput1;
where seed_data_files/in3.txt:
12 35
NULL40
48 NULL
100 100
I've tried:
SELECT * FROM myinput1 a FULL OUTER JOIN my
