Bug 1492642 - Regression of TEIID-4543 - Rewrite parse/format of standard formats to cast instead
Summary: Regression of TEIID-4543 - Rewrite parse/format of standard formats to cast i...
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid, Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 6.4.0
Assignee: David Le Sage
QA Contact: Andrej Smigala
Depends On:
TreeView+ depends on / blocked
Reported: 2017-09-18 11:41 UTC by Andrej Smigala
Modified: 2018-02-01 08:28 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Calls to PARSEDATE or PARSETIME which have a timestamp value as the first argument are now pushed as CONVERTs (otherwise they are pushed as regular PARSEDATEs or PARSETIMEs respectively).
Clone Of:
Last Closed: 2018-02-01 08:28:32 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4543 0 Major Resolved Rewrite parse/format of standard formats to cast instead 2018-08-07 15:27:47 UTC

Description Andrej Smigala 2017-09-18 11:41:59 UTC
Description of problem:

A regression was found for an enhancement originally introduced in 6.3.4. 

According to TEIID-4543, parsing a date or time from a string column using the PARSEDATE or PARSETIME functions should be pushed as simple cast in case the format string is the standard value ('yyyy-MM-dd' and 'hh:mm:ss' respectively).

However, running e.g.

    SELECT IntKey FROM Source.SmallA WHERE PARSEDATE(StringKey, 'yyyy-MM-dd') = {d'2016-12-19'}

with 6.4 ER2 shows the following in the query plan:

   AccessNode(0) output=[Source.smalla.intkey] SELECT g_0.intkey AS c_0 FROM Source.smalla AS g_0 WHERE convert(parsetimestamp(g_0.stringkey, 'yyyy-MM-dd'), date) = {d'2016-12-19'} LIMIT 100

i.e. there is still the call to parsetimestamp function.

Comment 6 David Le Sage 2017-12-05 22:37:20 UTC
Added as known issue errata to release notes.

Note You need to log in before you can comment on or make changes to this bug.