[
https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3219:
---------------------------------------
When I tested, I easily went into millions of iterations with out a
valid row.
Do you have an example of such a document? From my reading of the api the rows are stored
in treemaps and should represent the intended rows of the spreadsheet.
I suggested, look ahead on the row cursor for follow on column values
to check if they are null or not to define a value is null vs it is end of file. I asked
him configure the look-ahead number to be configurable.
That may not be appropriate either. If this kind of logic is needed, then it seems like
we could be checking the entire row rather than just what is projected to determine if
it's terminating (and based upon the above it may be optional behavior, such as
"terminate on all blank").
Excel Translator Wrong Result From Columns With Interleaved Null
Values
-----------------------------------------------------------------------
Key: TEIID-3219
URL:
https://issues.jboss.org/browse/TEIID-3219
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7.1
Reporter: Jan Stastny
Assignee: Kylin Soong
Fix For: 8.7.1, 8.10
Attachments: artifacts.zip
When querying a column which has a null value somewhere in it, the result set is missing
all the rows under the null value in the xlsx file. When querying more columns, the result
set is missing some values only if there is a row, where both columns contains null value.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)