[
https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4427:
---------------------------------------
i'm counting on ResultSetMetaDataImpl to create the view and
stage tables columns data types; in the case of Aggregate function COUNT, the meta is
returning Integer.
That is correct that count returns an integer. From that you are creating the DDL for a
mysql table? Are you mapping that to an unsigned int in mysql?
I'm still fuzzy on just exactly how the Teiid metadata for the materialization target
is being created. It seems from these comments that it must be happening via the
translator import - but that hasn't changed in any significant way in between the
releases in question.
Migration to Teiid 9.0.0 - Materialized views error: Expected
integer, but was bigdecimal
-----------------------------------------------------------------------------------------
Key: TEIID-4427
URL:
https://issues.jboss.org/browse/TEIID-4427
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.0
Reporter: Mark Tawk
Assignee: Steven Hawkins
Priority: Critical
Fix For: 9.1, 9.0.5
After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on
Oracle server.
when fetching an Oracle materialized view that contains a column using date function like
: "Month" or "Year" or "TIMESTAMPDIFF", we are getting the
error : Expected integer, but was bigdecimal.
If we go back to Teiid 8.11.3, the same materialized views fetch without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)