[
https://issues.jboss.org/browse/TEIID-4455?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4455:
---------------------------------------
The return type as string was later addressed - TEIID-5026
Teiid does not account for the timezone difference between source and
running instance (ignores DatabaseTimeZone property). It is serving exactly the same
timestamp as received from hive/impala instance, even though there's timezone
difference.
The calendar based methods (TEIID-3847) were are not supported by the driver, so the
property has no affect. It appears that is still the case for Hive -
https://github.com/apache/hive/blob/master/jdbc/src/java/org/apache/hive/...
Impala Translator - Change planning step for from_unixtime()
pushdown
---------------------------------------------------------------------
Key: TEIID-4455
URL:
https://issues.jboss.org/browse/TEIID-4455
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Reporter: Don Krapohl
Assignee: Kylin Soong
Priority: Minor
Labels: Impala_Translator
Fix For: 9.2, 8.12.15.6_4
Impala and Teiid both have from_unixtime() functions and per the forum reference the
mapping to timestampadd() appears to come before the test for pushdown support of the
impala native function.
As a query request we require the impala from_unixtime() function be executed instead of
the Teiid-native version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)