February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4751) Allow any collection type to be source of OBJECTTABLE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4751?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4751: --------------------------------------- For object table that just means array as well - or do you see anything else? For arrayIterator it will be unfortunately named and even more weakly typed as it currently requires an object[] argument. What about initially scoping this just to objecttable. > Allow any collection type to be source of OBJECTTABLE > ----------------------------------------------------- > > Key: TEIID-4751 > URL: https://issues.jboss.org/browse/TEIID-4751 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Currently Object table either accepts a single object or iterator/iterable as source to parse into results. This should be expanded to allow all collection types. > Same could be said for SYS.ArrayIterate procedure. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4294) External Materialization MATVIEW_AFTER_LOAD_SCRIPT may not be an atomic operation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4294?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4294: --------------------------------------- We will document 1 and 4. I'll see if it makes sense to pursue 2 as well. Given that we now have support for 4, we won't pursue 3. > External Materialization MATVIEW_AFTER_LOAD_SCRIPT may not be an atomic operation > --------------------------------------------------------------------------------- > > Key: TEIID-4294 > URL: https://issues.jboss.org/browse/TEIID-4294 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.2 > > Attachments: dv-2016-06-23-mat-view.log, teiid-command.log > > > Firstly, this issue appears even after *TEIID-4283* fix, and is db independent. > When during materialized view's loading there is a query on the view performed, timing issues appear. In MATVIEW_AFTER_LOAD_SCRIPT there might be more commands separated by semicolon, but these commands are not performed as a single operation. In specific timing a query on such view might fail when you have a MATVIEW_AFTER_LOAD_SCRIPT like this: > {code:sql} > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view''); > {code} > user might end up querying the view right in the moment, when 'primary' materialized table (dv_matviews_mat_view) was renamed (dv_matviews_mat_view_stage) and thus there's no such table like defined in the materialized view. > {code:xml} > CREATE VIEW external_long_ttl ( > customer_id integer NOT NULL, > total_amount integer > ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE', > MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable', > "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;', > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'IGNORE', > "teiid_rel:MATVIEW_TTL" 20000) > AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id; > {code} > Then for some queries I get: > {code:plain} > 10:40:19,252 WARN [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue130) Connector worker process failed for atomic-request=+k/MyS3sUhQX.14.7.113: org.teiid.translator.jdbc.JDBCExecutionException: 259 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."CUSTOMER_ID", g_0."TOTAL_AMOUNT" FROM "JSTASTNY".dvqe_X_XjdkY_YDV_MATVIEWS_MAT_VIEW AS g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-5.jar:8.12.5.redhat-5] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) > at sun.reflect.GeneratedMethodAccessor158.invoke(Unknown Source) [:1.7.0_79] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy80.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] > Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259]: invalid table name: Could not find table/view DVQE_X_XJDKY_YDV_MATVIEWS_MAT_VIEW in schema JSTASTNY: line 1 col 62 (at pos 61) > at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345) > at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:185) > at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:100) > at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1130) > at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:877) > at com.sap.db.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:410) > at com.sap.db.jdbc.CallableStatementSapDB.execute(CallableStatementSapDB.java:266) > at com.sap.db.jdbc.CallableStatementSapDB.executeQuery(CallableStatementSapDB.java:756) > at com.sap.db.jdbc.trace.PreparedStatement.executeQuery(PreparedStatement.java:161) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.5.redhat-5.jar:8.12.5.redhat-5] > ... 17 more > {code} > From the logs it seems that the after load script has completed, but probably not in the source db. In logs just before the exception I see: > {code:plain} > 12:34:59,247 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) Source-specific command: RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view > 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Executed command > 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Processing MORE request > 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Getting results from connector > 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Obtained last batch, total row count: 1 > 12:34:59,663 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Remove State > 12:34:59,664 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue79) ORTEkGreciAL.0.85.84 Processing Close : EXEC Source.native('RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view') > {code} > I attached the logs to this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4751) Allow any collection type to be source of OBJECTTABLE

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4751: ----------------------------------- Summary: Allow any collection type to be source of OBJECTTABLE Key: TEIID-4751 URL: https://issues.jboss.org/browse/TEIID-4751 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently Object table either accepts a single object or iterator/iterable as source to parse into results. This should be expanded to allow all collection types. Same could be said for SYS.ArrayIterate procedure. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4632) Clarify in doc's when a MAKEDEP temp table push down will be performed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4632?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4632. ----------------------------------- Resolution: Done Updated and corrected the text related to dependent joins. > Clarify in doc's when a MAKEDEP temp table push down will be performed > ---------------------------------------------------------------------- > > Key: TEIID-4632 > URL: https://issues.jboss.org/browse/TEIID-4632 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2 > > > Clarify in the documentation when the MAKEDEP temp table push down will be performed. It was tested and confirmed that by changing MaxInCriteriaSize to 1 and MaxDependentPredicates to 1 could force the temp table pushdown. So it would appear that when the number of independent values exceeds MaxInCriteriaSize*MaxDependentPredicates this would be performed (when Enabled Dependent Joins is true). > So, on page 832 (pdf of 9.1) > " .. then multiple dependent queries will be issued in parallel". > May want to rephrase to say if "Enabled Dependent Joins" is true, that pushed down to temp table will occur, other wise, multiple dependent queries will be issued in parallel. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4717: ------------------------------------- [~vijaynm] +1 for your idea on single table. That way we do not inadvertently introduce something we are not aware of. > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As a user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Vijay K (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Vijay K edited comment on TEIID-4717 at 2/9/17 8:02 AM: -------------------------------------------------------- [~rareddy] what is your suggestion? do it for all the tables or specific tables? was (Author: vijaynm): [~rareddy] what is your suggestion? do it for all the tables or at tables? > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As a user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Vijay K (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Vijay K commented on TEIID-4717: -------------------------------- [~rareddy] what is your suggestion? do it for all the tables or at tables? > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As a user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4747) Support queries with Oracle outer join operator (+)

by Rafael Coutinho (JIRA)

[ https://issues.jboss.org/browse/TEIID-4747?page=com.atlassian.jira.plugin... ] Rafael Coutinho resolved TEIID-4747. ------------------------------------ Resolution: Done > Support queries with Oracle outer join operator (+) > ---------------------------------------------------- > > Key: TEIID-4747 > URL: https://issues.jboss.org/browse/TEIID-4747 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Priority: Minor > Labels: oracle, teiid-engine > > Oracle defines the > operator $+$ for outer joins > http://docs.oracle.com/cd/B28359_01/server.111/b28286/queries006.htm#SQLR.... > We are trying use JDV as the source of an external product (Business Object) which uses those oracle operators. We cannot change the way that product generates the queries, and it does use the $+$ operator, failing the integration with a JDV underlying database. > Is there a way to parse that outer join notation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4747) Support queries with Oracle outer join operator (+)

by Rafael Coutinho (JIRA)

[ https://issues.jboss.org/browse/TEIID-4747?page=com.atlassian.jira.plugin... ] Rafael Coutinho closed TEIID-4747. ---------------------------------- > Support queries with Oracle outer join operator (+) > ---------------------------------------------------- > > Key: TEIID-4747 > URL: https://issues.jboss.org/browse/TEIID-4747 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Priority: Minor > Labels: oracle, teiid-engine > > Oracle defines the > operator $+$ for outer joins > http://docs.oracle.com/cd/B28359_01/server.111/b28286/queries006.htm#SQLR.... > We are trying use JDV as the source of an external product (Business Object) which uses those oracle operators. We cannot change the way that product generates the queries, and it does use the $+$ operator, failing the integration with a JDV underlying database. > Is there a way to parse that outer join notation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4747) Support queries with Oracle outer join operator (+)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4747?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4747: --------------------------------------- Yes, it was added with TEIID-3369 in 8.11. There was also a thought at some point to allow a PreParsers to be VDB scoped as well, but that has not been added yet. > Support queries with Oracle outer join operator (+) > ---------------------------------------------------- > > Key: TEIID-4747 > URL: https://issues.jboss.org/browse/TEIID-4747 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Rafael Coutinho > Assignee: Steven Hawkins > Priority: Minor > Labels: oracle, teiid-engine > > Oracle defines the > operator $+$ for outer joins > http://docs.oracle.com/cd/B28359_01/server.111/b28286/queries006.htm#SQLR.... > We are trying use JDV as the source of an external product (Business Object) which uses those oracle operators. We cannot change the way that product generates the queries, and it does use the $+$ operator, failing the integration with a JDV underlying database. > Is there a way to parse that outer join notation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017