April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4131) External Materialized View's initial status should not insert into SYSADMIN.MatViews

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4131?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4131. ----------------------------------- Fix Version/s: (was: 9.x) Resolution: Rejected The intent of this view is to show all materialized views - internal and external. Since we locally maintain the state for the internal status it is shown here, but for performance and other considerations we don't show the external status. > External Materialized View's initial status should not insert into SYSADMIN.MatViews > ------------------------------------------------------------------------------------ > > Key: TEIID-4131 > URL: https://issues.jboss.org/browse/TEIID-4131 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > > During VDB deploying, External Materialized View's initial status be insert into SYSADMIN.MatViews, this cause stale data, due to External Materialized View's status should go into physical database. Below is a example > {code} > SQL: SELECT VDBName, SchemaName, Name, TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality FROM SYSADMIN.MatViews > +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ > | VDBName | SchemaName | Name | TargetSchemaName | TargetName | Valid | LoadState | Updated | Cardinality | > +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ > | PortfolioMaterialize | pg_catalog | matpg_datatype | [NULL] | #MAT_PG_CATALOG.MATPG_DATATYPE | false | NEEDS_LOADING | [NULL] | [NULL] | > | PortfolioMaterialize | pg_catalog | pg_type | [NULL] | #MAT_PG_CATALOG.PG_TYPE | false | NEEDS_LOADING | [NULL] | [NULL] | > | PortfolioMaterialize | StocksMatModel | stockPricesMatView | Accounts | H2_STOCK_MAT | [NULL] | [NULL] | [NULL] | [NULL] | > | PortfolioMaterialize | StocksMatModel_1 | stockPricesMatView_1 | Accounts | H2_STOCK_MAT_1 | [NULL] | [NULL] | [NULL] | [NULL] | > | PortfolioMaterialize | StocksMatModel_2 | stockPricesMatView_2 | Accounts | H2_STOCK_MAT_2 | [NULL] | [NULL] | [NULL] | [NULL] | > | PortfolioMaterialize | StocksMatModel_3 | stockPricesMatView_3 | Accounts | H2_STOCK_MAT_3 | [NULL] | [NULL] | [NULL] | [NULL] | > | PortfolioMaterialize | SYS | spatial_ref_sys | [NULL] | #MAT_SYS.SPATIAL_REF_SYS | false | NEEDS_LOADING | [NULL] | [NULL] | > +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ > {code} > Note that stockPricesMatView, stockPricesMatView_1, stockPricesMatView_2, stockPricesMatView_3 should not go into SYSADMIN.MatViews -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4112) ORA-32039: recursive WITH clause must have column alias list

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIID-4112?page=com.atlassian.jira.plugin... ] Andrej Šmigala updated TEIID-4112: ---------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/666 > ORA-32039: recursive WITH clause must have column alias list > ------------------------------------------------------------ > > Key: TEIID-4112 > URL: https://issues.jboss.org/browse/TEIID-4112 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > If running a WITH table AS(...) query to Oracle and the query schema name is the same as the subquery name i.e. EWI. you receive the Oracle error: > ORA-32039: recursive WITH clause must have column alias list > If you modify the query to > WITH EWI1 AS .... > then it works. > f.ex: > breaking: WITH tbl AS ( > where tbl = a common table name in the current schema and the common table definition as (...) references a view in that schema. Oracle will complain with this erroneous error. > work-around: WITH tbl_1 AS( > where tbl_1 does not exist as a current schema/table name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4132) Internal Mat View's teiid_rel:MATVIEW_PREFER_MEMEORY option not take effect

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4132: ---------------------------------- Summary: Internal Mat View's teiid_rel:MATVIEW_PREFER_MEMEORY option not take effect Key: TEIID-4132 URL: https://issues.jboss.org/browse/TEIID-4132 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.x Reporter: Kylin Soong Assignee: Steven Hawkins Fix For: 9.x >From [https://teiid.gitbooks.io/documents/content/caching/Internal_Materializat...], the "teiid_rel:MATVIEW_PREFER_MEMEORY" should be same as the pref_mem cache hint option. But in my debug, it's not convert to cache hint, for example, {code} ) OPTIONS (materialized true, UPDATABLE 'TRUE', "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', "teiid_rel:MATVIEW_PREFER_MEMEORY" 'true', "teiid_rel:MATVIEW_TTL" 300000, "teiid_rel:MATVIEW_UPDATABLE" 'true', "teiid_rel:MATVIEW_SCOPE" 'VDB' ) {code} In TempTableDataManager's loadGlobalTable() method, the cache hint is like {code} /*+ cache(updatable scope:VDB) */ {code} also the _hint.isPrefersMemory()_ result is false. So how to understand "teiid_rel:MATVIEW_PREFER_MEMEORY" in internal mat? does this is expect behivior? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4131) External Materialized View's initial status should not insert into SYSADMIN.MatViews

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4131: ---------------------------------- Summary: External Materialized View's initial status should not insert into SYSADMIN.MatViews Key: TEIID-4131 URL: https://issues.jboss.org/browse/TEIID-4131 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.x Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x During VDB deploying, External Materialized View's initial status be insert into SYSADMIN.MatViews, this cause stale data, due to External Materialized View's status should go into physical database. Below is a example {code} SQL: SELECT VDBName, SchemaName, Name, TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality FROM SYSADMIN.MatViews +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ | VDBName | SchemaName | Name | TargetSchemaName | TargetName | Valid | LoadState | Updated | Cardinality | +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ | PortfolioMaterialize | pg_catalog | matpg_datatype | [NULL] | #MAT_PG_CATALOG.MATPG_DATATYPE | false | NEEDS_LOADING | [NULL] | [NULL] | | PortfolioMaterialize | pg_catalog | pg_type | [NULL] | #MAT_PG_CATALOG.PG_TYPE | false | NEEDS_LOADING | [NULL] | [NULL] | | PortfolioMaterialize | StocksMatModel | stockPricesMatView | Accounts | H2_STOCK_MAT | [NULL] | [NULL] | [NULL] | [NULL] | | PortfolioMaterialize | StocksMatModel_1 | stockPricesMatView_1 | Accounts | H2_STOCK_MAT_1 | [NULL] | [NULL] | [NULL] | [NULL] | | PortfolioMaterialize | StocksMatModel_2 | stockPricesMatView_2 | Accounts | H2_STOCK_MAT_2 | [NULL] | [NULL] | [NULL] | [NULL] | | PortfolioMaterialize | StocksMatModel_3 | stockPricesMatView_3 | Accounts | H2_STOCK_MAT_3 | [NULL] | [NULL] | [NULL] | [NULL] | | PortfolioMaterialize | SYS | spatial_ref_sys | [NULL] | #MAT_SYS.SPATIAL_REF_SYS | false | NEEDS_LOADING | [NULL] | [NULL] | +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+ {code} Note that stockPricesMatView, stockPricesMatView_1, stockPricesMatView_2, stockPricesMatView_3 should not go into SYSADMIN.MatViews -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4130) Prevent blocked exceptions from being thrown in AccessNode open

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4130?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4130. ----------------------------------- Resolution: Done Added a catch block to prevent blocked exceptions from going further and allowed the open operations to continue in the next batch method. > Prevent blocked exceptions from being thrown in AccessNode open > --------------------------------------------------------------- > > Key: TEIID-4130 > URL: https://issues.jboss.org/browse/TEIID-4130 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.4 > > > Having the access node block in open can lead to unintended consequences in parent nodes. For example with tuplesource caching it can create additional tuplesource instances such the cached source is closed prematurely (as it thinks that all readers have been satisfied). This results in exceptions similar to: > TEIID30019 Unexpected exception for request 2TLgULsEBZvO.8: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null > ... > at org.teiid.common.buffer.TupleBuffer.getBatch(TupleBuffer.java:286) \[teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1] > at org.teiid.dqp.internal.process.TupleSourceCache$CopyOnReadTupleSource.nextTuple(TupleSourceCache.java:103) \[teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1] > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4130) Prevent blocked exceptions from being thrown in AccessNode open

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4130: ------------------------------------- Summary: Prevent blocked exceptions from being thrown in AccessNode open Key: TEIID-4130 URL: https://issues.jboss.org/browse/TEIID-4130 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.5, 8.13.4 Having the access node block in open can lead to unintended consequences in parent nodes. For example with tuplesource caching it can create additional tuplesource instances such the cached source is closed prematurely (as it thinks that all readers have been satisfied). This results in exceptions similar to: TEIID30019 Unexpected exception for request 2TLgULsEBZvO.8: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null ... at org.teiid.common.buffer.TupleBuffer.getBatch(TupleBuffer.java:286) \[teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1] at org.teiid.dqp.internal.process.TupleSourceCache$CopyOnReadTupleSource.nextTuple(TupleSourceCache.java:103) \[teiid-engine-8.7.5.6_2-redhat-1.jar:8.7.5.6_2-redhat-1] ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4129) Wrong results with cross model join on 2 varchar fields

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4129?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4129: --------------------------------------- Can you provide a vdb for this? Also what specifically are the source types - just varchar or case-insensitive, fixed length char, etc.? > Wrong results with cross model join on 2 varchar fields > ------------------------------------------------------- > > Key: TEIID-4129 > URL: https://issues.jboss.org/browse/TEIID-4129 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > Attachments: H2 DBs.zip > > > I'm using Teiid 8.11.3 with H2 translator. > I'm joining 2 h2 tables from 2 different teiid models linked on varchar fields. > the query result is retuning empty values from the joined table even though the joined values are identical. > You find attached a zip file containing 2 h2 DBs for a simplified example > Here is the query used: > _select "Customer"."City" as "Customer_City","Customer"."CustomerID" as "Customer_CustomerID","City"."City" as "City_City","City"."CityID" as "City_CityID" > from "db2"."Customer" "Customer" > LEFT JOIN "db1"."City" "City" ON "Customer"."City" = "City"."City"_ > Note that if the 2 tables are in the same model, the query return correct results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4129) Wrong results with cross model join on 2 varchar fields

by Mark Tawk (JIRA)

Mark Tawk created TEIID-4129: -------------------------------- Summary: Wrong results with cross model join on 2 varchar fields Key: TEIID-4129 URL: https://issues.jboss.org/browse/TEIID-4129 Project: Teiid Issue Type: Bug Reporter: Mark Tawk Assignee: Steven Hawkins Attachments: H2 DBs.zip I'm using Teiid 8.11.3 with H2 translator. I'm joining 2 h2 tables from 2 different teiid models linked on varchar fields. the query result is retuning empty values from the joined table even though the joined values are identical. You find attached a zip file containing 2 h2 DBs for a simplified example Here is the query used: _select "Customer"."City" as "Customer_City","Customer"."CustomerID" as "Customer_CustomerID","City"."City" as "City_City","City"."CityID" as "City_CityID" from "db2"."Customer" "Customer" LEFT JOIN "db1"."City" "City" ON "Customer"."City" = "City"."City"_ Note that if the 2 tables are in the same model, the query return correct results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4128) Domain mode - full-ha profile does not disable SSL for ODBC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4128?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4128: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1323563|https://bugzilla.redhat.com/show_bug.cgi?id=1323563] from ASSIGNED to MODIFIED > Domain mode - full-ha profile does not disable SSL for ODBC > ----------------------------------------------------------- > > Key: TEIID-4128 > URL: https://issues.jboss.org/browse/TEIID-4128 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > "full-ha" profile in the domain mode is missing default SSL configuration for ODBC transport: > <ssl mode="disabled"/> > This prevents OOB user:password authentication for ODBC transport. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4128) Domain mode - full-ha profile does not disable SSL for ODBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4128?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4128. ----------------------------------- Fix Version/s: 8.12.5 Resolution: Done Merged the pull request. It looks like later branches were already corrected. > Domain mode - full-ha profile does not disable SSL for ODBC > ----------------------------------------------------------- > > Key: TEIID-4128 > URL: https://issues.jboss.org/browse/TEIID-4128 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.5 > > > "full-ha" profile in the domain mode is missing default SSL configuration for ODBC transport: > <ssl mode="disabled"/> > This prevents OOB user:password authentication for ODBC transport. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016