[
https://issues.jboss.org/browse/TEIID-5026?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5026.
-----------------------------------
Resolution: Done
For 10.0 resolved with a breaking change to align the from_unixtime function to the
definition used by hive/impala - which were the only sources marked as supporting the
pushdown. Sources supporting timestampadd will no longer have a compensating version of
from_unixtime pushed as it only supports integers and returns a timestamp, not a string.
Additionally unix_timestamp was added for the inverse operation - string to long. Neither
function yet supports a format string, but rather assume the default format.
For those that may need conversion to and from milliseconds the related to_millis and
from_millis.
Add function to transform timestamp into Unix time
--------------------------------------------------
Key: TEIID-5026
URL:
https://issues.jboss.org/browse/TEIID-5026
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Jan Stastny
Assignee: Steven Hawkins
Fix For: 10.0
Teiid supports function FROM_UNIXTIME as a result of TEIID-248.
There isn't its reverse counterpart though.
This is an issue, when there is a data source which doesn't support
timestamp/date/time data types:
* users choose to use long(unix time) in the source
* by using FROM_UNIXTIME function they transform the long value (unix time) into
respective data type value in their virtual model
* they can read such source.
* they can't insert/update it as this would require 'INSTEAD OF TRIGGER' with
ability to transform timestamp/time/date back to long value - Unix time. This part is
missing.
As an example could serve [MySQL's
UNIX_TIMESTAMP|https://dev.mysql.com/doc/refman/5.5/en/date-and-time-func...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)