[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3543:
-------------------------------------
Steve, the commit is on the master, but fix version shows 8.11. Also, I may have omitted the same in V4, I would like to fix in that code base too before 8.11 final
> Complex type values not resolved in translator execution
> --------------------------------------------------------
>
> Key: TEIID-3543
> URL: https://issues.jboss.org/browse/TEIID-3543
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception:
> {code}
> java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails
> at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3547?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3547:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1233212|https://bugzilla.redhat.com/show_bug.cgi?id=1233212] from NEW to MODIFIED
> Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3547
> URL: https://issues.jboss.org/browse/TEIID-3547
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator
> [1]
> *Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [2]
> *Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [3]
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3543) Complex type values not resolved in translator execution
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3543:
---------------------------------------
I should add that a re-import of the metadata is required as the complex_type property needs the fqn, not just the name, of the complex type.
> Complex type values not resolved in translator execution
> --------------------------------------------------------
>
> Key: TEIID-3543
> URL: https://issues.jboss.org/browse/TEIID-3543
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception:
> {code}
> java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails
> at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3547?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3547.
-----------------------------------
Resolution: Duplicate Issue
TEIID-3269 addressed this already. It was net yet back ported.
> Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3547
> URL: https://issues.jboss.org/browse/TEIID-3547
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator
> [1]
> *Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [2]
> *Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [3]
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3547?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3547:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1233212
> Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3547
> URL: https://issues.jboss.org/browse/TEIID-3547
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator
> [1]
> *Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [2]
> *Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> [3]
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
> *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1;
> *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3547:
-----------------------------------
Summary: Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character
Key: TEIID-3547
URL: https://issues.jboss.org/browse/TEIID-3547
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7.1.6_2
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator
[1]
*Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1;
*Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
[2]
*Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1;
*Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
[3]
*Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1;
*Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
*Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1;
*Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months