[
https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4427:
---------------------------------------
Shouldn't Teiid be expecting the same type returned by the meta?
It is. You are saying that Teiid is complaining "Expected integer, but was
long" - that indicates that the view has an integer column, but the materialization
table that we are trying to substitute for the view has a long column instead. What
I'm suspecting is that an unsigned int column is being used to define the mysql table,
then the translator importer is defining that as a long in Teiid. Can you confirm how the
mysql materialization target table is being imported into Teiid? And if the int column in
mysql is unsigned?
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)