[
https://issues.apache.org/jira/browse/ASTERIXDB-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401549#comment-15401549
]
Michael J. Carey commented on ASTERIXDB-1558:
---------------------------------------------
Can you paste a short explanation here of *why* that table is what it is in the
(upper right) corner case that we're addressing here? I.e., if something is
MISSING (as opposed to NULL), wouldn't it kind of be expected that IS NULL
should simply be FALSE and IS NOT NULL should be TRUE? What am I MISSING in
thinking that the current "design" is wierd? (What were we thinking...? There
must have been a seemingly good reason.)
> Possible minor glitch in UNKNOWN value related predicates/handling
> ------------------------------------------------------------------
>
> Key: ASTERIXDB-1558
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1558
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Translator - AQL
> Reporter: Michael J. Carey
> Assignee: Yingyi Bu
> Priority: Minor
>
> The following evaluates to TRUE:
> {
> 'project': 'AsterixDB',
> 'members': [ 'vinayakb', 'dtabass', 'chenli', 'tsotras' ]
> }.member IS MISSING;
> As, desirably, does:
> {
> 'project': 'AsterixDB',
> 'members': [ 'vinayakb', 'dtabass', 'chenli', 'tsotras' ]
> }.member IS UNKNOWN;
> But the following evaluates to NULL (and it seems to me that FALSE would be
> the proper expected result):
> {
> 'project': 'AsterixDB',
> 'members': [ 'vinayakb', 'dtabass', 'chenli', 'tsotras' ]
> }.member IS NULL;
> Of course, I could be MISSING something here, as a SQL++ newbie....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
