Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1351987

Summary:	Accumulo translator: null values not returned for <> criteria in WHERE clause
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Jan Stastny <jstastny>
Component:	Teiid	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NOTABUG	QA Contact:	Jan Stastny <jstastny>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.3.0	CC:	aszczucz, blafond, drieden, jolee, mbaluch, thauser, vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-06 13:32:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.