[
https://issues.jboss.org/browse/TEIID-3118?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-3118.
---------------------------------
Labels: Beta1 (was: )
Fix Version/s: 8.7.1
8.9
Resolution: Done
Excel supports WHERE clause push down only on ROW_ID, in this case it is being handled by
the engine. However this is what I see. When engine builds the java.sql.Time instance it
from Epoach, where as the java.sql.Time object that is built in Excel is from a date type
that Apache POI returns. Even though the time value is correct the date value is not from
these both instances thus they do not match.
The solution is just to extract the Time specific value from Excel instance and build the
Time result.
Excel translator is not able to manage WHERE clause with time value
-------------------------------------------------------------------
Key: TEIID-3118
URL:
https://issues.jboss.org/browse/TEIID-3118
Project: Teiid
Issue Type: Bug
Reporter: Juraj DurĂ¡ni
Assignee: Ramesh Reddy
Labels: Beta1
Fix For: 8.7.1, 8.9
Excel translator is not able to manage WHERE clause with time value. When I use time
value in WHERE clause (with <, >, =) I get bad result. There is no problem with
Timestamp and Date.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)