September 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4440) Add an option to materialize common tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4440?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4440: ---------------------------------- Component/s: Grammar > Add an option to materialize common tables > ------------------------------------------ > > Key: TEIID-4440 > URL: https://issues.jboss.org/browse/TEIID-4440 > Project: Teiid > Issue Type: Feature Request > Components: Grammar, Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > In addition to the no_inline hint, there should be a materialize hint to force a common table to be evaluated as a table, rather than eligible for partial pushdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4243) Use BatchUpdateException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4243?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4243. ----------------------------------- Resolution: Done Updated the internal and exception handling to support conveying where a batch fails. > Use BatchUpdateException > ------------------------ > > Key: TEIID-4243 > URL: https://issues.jboss.org/browse/TEIID-4243 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > An invalid early assumption was that the a batched update would typically be performed atomically - however updates that span non-xa sources violate this assumption. Also a wrapping transaction is not required by JDBC in auto commit true mode the updates are still logically performed individually. We need to allow for BatchUpdateException to convey which updates actually succeeded and were attempted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4427: ---------------------------------- In the method checkForUnsigned in JDBCMetdataProcessor.java The view with count fetched successfully in those 2 cases: 1- assign widenUnsingedTypes to false or 2- When INTEGER, I changed the sqlType from Types.BIGINT to Types.INTEGER. > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk edited comment on TEIID-4427 at 9/14/16 11:03 AM: ------------------------------------------------------------ You are right concerning the error, i thought Teiid was expecting long. The data type i'm using in mysql target table is int(10), i have also tried int and integer, and got the same error. The case is easily reproduced when you materialize a view containing a count over Mysql or Oracle. > Can you confirm how the mysql materialization target table is being imported into Teiid? I did not get what you mean, the target table name is assigned into the view creation sql was (Author: mtawk): You are right concerning the error, i thought he was expecting long. The data type i'm using in mysql target table is int(10), i have also tried int and integer, and got the same error. The case is easily reproduced when you materialize a view containing a count over Mysql or Oracle. > Can you confirm how the mysql materialization target table is being imported into Teiid? I did not get what you mean, the target table name is assigned into the view creation sql > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4427: ---------------------------------- You are right concerning the error, i thought he was expecting long. The data type i'm using in mysql target table is int(10), i have also tried int and integer, and got the same error. The case is easily reproduced when you materialize a view containing a count over Mysql or Oracle. > Can you confirm how the mysql materialization target table is being imported into Teiid? I did not get what you mean, the target table name is assigned into the view creation sql > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Steven Hawkins (JIRA)

[ 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4427: ---------------------------------- In my case the argument for MAX is of type int > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk edited comment on TEIID-4427 at 9/14/16 9:55 AM: ----------------------------------------------------------- Integer is interpreted to int in mysql Long is interpreted to bigint in mysql But Teiid is expecting Long for COUNT while the meta for creating the materialized view structure is returning Integer. Shouldn't Teiid be expecting the same type returned by the meta? was (Author: mtawk): Integer is interpreted to int in mysql Long is interpreted to bigint in mysql But Teiid is expecting Long for COUNT while the meta for creating the materialized view structure is returning Integer > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4427: ---------------------------------- Integer is interpreted to int in mysql Long is interpreted to bigint in mysql But Teiid is expecting Long for COUNT while the meta for creating the materialized view structure is returning Integer > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4427: --------------------------------------- > When using MAX aggregate function, the source code I sent in the previous message return Long The return value for max will depend upon the argument type. count will always return integer. > 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)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2016