[teiid-issues] [JBoss JIRA] (TEIID-5297) With MongoDB, null is returned from timestamp functions if the same function is part of WHERE clause

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5297.
-----------------------------------
    Fix Version/s: 10.3
                   10.1.3
                   10.0.5
                   10.2.1
       Resolution: Done


Updated the logic to reuse the implicit alias of functions.

> With MongoDB, null is returned from timestamp functions if the same function is part of WHERE clause
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-5297
>                 URL: https://issues.jboss.org/browse/TEIID-5297
>             Project: Teiid
>          Issue Type: Bug
>          Components: Misc. Connectors
>    Affects Versions: 8.12.11.6_4
>            Reporter: Jan Martiska
>            Assignee: Steven Hawkins
>             Fix For: 10.3, 10.1.3, 10.0.5, 10.2.1
>
>
> For example:
> {noformat}
> SELECT timestampvalue, second(timestampvalue) as sec FROM bqt1.hugeA WHERE second(timestampvalue) >= 0
> {noformat}
> This will correctly select rows where {{second(timestampvalue) >= 0}}, but the {{sec}} column in the result will contain only nulls.
> If I remove the WHERE clause:
> {noformat}
> SELECT timestampvalue, second(timestampvalue) as sec FROM bqt1.hugeA;
> {noformat}
> Then the {{sec}} column will be computed correctly.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)