Bug 1351987 - Accumulo translator: null values not returned for <> criteria in WHERE clause
Summary: Accumulo translator: null values not returned for <> criteria in WHERE clause
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-01 10:37 UTC by Jan Stastny
Modified: 2016-07-11 15:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-06 13:32:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4316 0 Major Resolved Accumulo translator: null values not returned for <> criteria in WHERE clause 2016-08-30 11:16:07 UTC

Description Jan Stastny 2016-07-01 10:37:02 UTC 
Description of problem:
For columns, which contain some null values, a query like:

SELECT nullable_column FROM table_name WHERE nullable_column <> some_value

doesn't return null values.

Expected results:
resultset with null values

Version:
DV 6.3.0 ER5
Comment 1 JBoss JIRA Server 2016-07-06 13:21:42 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-4316 to Resolved
Comment 2 Van Halbert 2016-07-06 13:32:31 UTC 
Per the comment of the engineer:

Almost all sources should support three-valued null logic.  As Ramesh is showing with Postgresql, a comparison with null will evaluate to unknown, which will not pass as true in a where clause, thus no null rows.
Note You need to log in before you can comment on or make changes to this bug.