>Obviously, the expected answer is always 2. That's incorrect. It's expected behaviour, SQL standard and I would expect every other DBs behave same way. The direct comparison to NULL returns FALSE. Always. Doesn't matter if used as <> ,=, IN, NOT IN. IS (NOT) NULL is the right way to handle such cases. COALESCE is some alternative too.
Thank you, Kind Regards ~Maciek On Tue, Jul 7, 2015 at 11:46 AM, Furcy Pin <[email protected]> wrote: > Hi folks, > > just to let my fellow Hive users know that we found a bug with subquery in > where clauses and created a JIRA for it. > > https://issues.apache.org/jira/browse/HIVE-11192 > > The latest version seems to be affected. > > Regards, > > Furcy Pin >
