[
https://issues.apache.org/jira/browse/HIVE-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978656#comment-15978656
]
Zoltan Haindrich commented on HIVE-13583:
-----------------------------------------
[~ashutoshc],[~pxiong]: I see a few tickets which are connected in some way,
but the others are related to parsing booleans/etc....so I think this is the
most important from all of them...the standard states that search conditions
should support {{UNKNOWN}} which is entirely unsupported currently - I would
like to try with the following approach:
* add {{UNKNOWN}} as an alias to {{NULL}}
* enable standard binary operators to follow the truth tables defined for
search conditions for {{NULL and TRUE}}
* ...and make parsing coherent with these changes :)
there would be some sideeffects of this, like:
* {{UNKNOWN = NULL}} is true
* {{select UNKNOWN}} is null
about the other path: declaring {{UNKNOWN}} as a completely different thing;
would require even changing the binary op handling codes in vectorization also
( it currently uses boolean[]; but I've read somewhere that the move to
{{BitSet}} is planned)
what do you think about this approach?
> E061-14: Search Conditions
> --------------------------
>
> Key: HIVE-13583
> URL: https://issues.apache.org/jira/browse/HIVE-13583
> Project: Hive
> Issue Type: Sub-task
> Reporter: Carter Shanklin
>
> This is a part of the SQL:2011 Analytics Complete Umbrella JIRA HIVE-13554.
> Support for various forms of search conditions are mandatory in the SQL
> standard. For example, "<predicate> is not true;" Hive should support those
> forms mandated by the standard.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
