[
https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin...
]
Jan Stastny reopened TEIID-3929:
--------------------------------
The problem is still there.
If I select only nullable column, there are no NULL values returned, even though they
should. Such query:
{code:sql}
SELECT bytenum FROM bqt1.smalla;
{code} returns 47 rows.
When I add a column, which in fact is a mapped rowid from accumulo table, I get same
number of results - no NULLs returned:
{code:sql}
SELECT intkey,bytenum FROM bqt1.smalla;
{code} returns 47 rows.
Even though the query on the 'rowid' column:
{code:sql}
SELECT intkey FROM bqt1.smallA;
{code} returns 50 rows.
But when I select with not nullable column (stringkey), which is not the rowid in
accumulo, I get correct results.
{code:sql}
SELECT stringkey,bytenum FROM bqt1.smalla;
{code} returns 50 rows with null values.
Accumulo does not return null values
------------------------------------
Key: TEIID-3929
URL:
https://issues.jboss.org/browse/TEIID-3929
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.3
Reporter: Jan Stastny
Assignee: Ramesh Reddy
Fix For: 9.0, 8.12.5
Accumulo doesn't return null values when a whole 'column' is being selected.
For a command in accumulo shell like:
{code:plain}
scan -c name:BYTENUM
{code}
Accumulo returns only non-empty values, this is expected behaviour.
Equivalent query in Teiid would be:
{code:sql}
SELECT ByteNum FROM SmallA
{code}
Which returns the same results as Accumulo does. That means, no NULL values, if there are
rowids without specified column families/qualifiers missing. But when a user has his
schema defined in a vdb, he probably expects, that he will get as many rows as there are
in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)