[JBoss JIRA] (TEIID-4576) Do not get rid of an excepiton in BasicCryptor.decrypt()
by Hiroki Daicho (JIRA)
[ https://issues.jboss.org/browse/TEIID-4576?page=com.atlassian.jira.plugin... ]
Hiroki Daicho commented on TEIID-4576:
--------------------------------------
JDV and Java version is as follows.
- Server
- JDV 6.2.4 (Teiid 8.7.1.6 )
- JRE 1.7.0 IBM J9 2.7 AIX ppc64-64 20140707_205525
java.fullversion = JRE 1.7.0 IBM J9 2.7 AIX ppc64-64 20140707_205525 (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR1_20140707_1408_B205525
JIT - tr.r13.java_20140410_61421.07
GC - R27_Java727_SR1_20140707_1408_B205525
J9CL - 20140707_205525
- Client
- teiid-8.4.1-redhat-7-jdbc.jar
- JRE 1.7.0 IBM J9 2.6 AIX ppc64-64 20140106_181350
java version "1.7.0"
Java(TM) SE Runtime Environment (build pap6470sr6fp1-20140108_01(SR6 FP1))
IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc64-64 Compressed References
20140106_181350 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR6_20140106_1601_B181350
JIT - r11.b05_20131003_47443.02
GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS
J9CL - 20140106_181350)
JCL - 20140103_01 based on Oracle 7u51-b11
A single query was sent by JDBC Driver loaded via java.sql.DriverManager.
The server has worked a some days, and the query was sent on a day once in every midnight.
The exception was occurred once.
> Do not get rid of an excepiton in BasicCryptor.decrypt()
> --------------------------------------------------------
>
> Key: TEIID-4576
> URL: https://issues.jboss.org/browse/TEIID-4576
> Project: Teiid
> Issue Type: Feature Request
> Components: Common
> Affects Versions: 8.12.6.6_3
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
>
> org.teiid.core.crypto.BasicCryptor.decrypt() disposes of an exception which is caught there, but it is necessary for investigation when an error occurs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4552) Missing support for connection to Facebook via OAuth 2
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4552?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-4552:
------------------------------------
Okay, let me look more.
> Missing support for connection to Facebook via OAuth 2
> ------------------------------------------------------
>
> Key: TEIID-4552
> URL: https://issues.jboss.org/browse/TEIID-4552
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 8.12.5
> Reporter: Lucie Fabrikova
> Assignee: Kylin Soong
> Fix For: 9.2
>
> Attachments: facebook3-vdb.xml, query, server.log, standalone.xml, teiid-oauth-util.sh-output
>
>
> I would like to connect to facebook resource adapter and configure OAuth 2 security domain for it; I used teiid-oauth-util.sh to generate the security domain (see attachment). Facebook doesn't support refresh tokens and in the generated code is refresh token's value "null".
> If I try to execute VDB with source pointing to such resource adapter I get error:
> ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Gapuea1/NRcn.6.3.0: org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException
>
> (see server.log, facebook-vdb.xml, standalone.xml)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4565) Add objects table to system schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4565?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4565:
----------------------------------
Component/s: Query Engine
Fix Version/s: 9.2
More than likely we'll implement this internally as we already maintain an all objects set.
> Add objects table to system schema
> ----------------------------------
>
> Key: TEIID-4565
> URL: https://issues.jboss.org/browse/TEIID-4565
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Tom Johnston
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> The addition of a objects table would make it simpler to join to when extensions are implemented.
> An example might be something similar to this query:
> select sysObjects.*
> from (
> select t.schemaName as Parent,t.name, t.uid ,'Table' as ObjectType
> from sys.tables t
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select c.tableName as Parent,c.name, c.uid,'Column' as ObjectType
> from sys.columns c
> where schemaName not in (select distinct(schemaName) from "SYS"."Tables" where isSystem = true)
> UNION
> select null as Parent,e.Value as Name,e.uid,'Property' as ObjectType
> from sys.properties as e) as SysObjects
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4579) External Materialization MySQL can't swap primary and stage table in xa transaction
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4579?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4579:
---------------------------------------
Jan, is it possible for you to test using the rename statement so that we can resolve this as a doc issue?
> External Materialization MySQL can't swap primary and stage table in xa transaction
> -----------------------------------------------------------------------------------
>
> Key: TEIID-4579
> URL: https://issues.jboss.org/browse/TEIID-4579
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.12.7.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> When using MySQL 5.5 as materialization target (primary and stage table are placed there) and on server side the mysql datasource is configured as xa-datasource, problem with transaction scope and status appears.
> The cause of this issue is, that in my "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" I try to swap primary and stage materialization tables by using third swap table:
> {code:sql}
> exec Source.native(''ALTER TABLE DV_MATVIEWS_MAT_VIEW_STAGE RENAME TO DV_MATVIEWS_MAT_VIEW_TEMP'');
> exec Source.native(''ALTER TABLE DV_MATVIEWS_MAT_VIEW RENAME TO DV_MATVIEWS_MAT_VIEW_STAGE'');
> exec Source.native(''ALTER TABLE DV_MATVIEWS_MAT_VIEW_TEMP RENAME TO DV_MATVIEWS_MAT_VIEW'');
> {code}
> but there is a limitation of ALTER TABLE commands which results in implicit commit:
> https://dev.mysql.com/doc/refman/5.5/en/implicit-commit.html
> Eventually the first of the three ALTER commands succeeds, but the second fails, thus I end up with no DV_MATVIEWS_MAT_VIEW_STAGE table, as it was previously renamed to DV_MATVIEWS_MAT_VIEW_TEMP. This particular problem could be resolved by TEIID-4240 I believe.
> The stacktrace of the issue:
> {code:plain}
> 15:19:59,825 DEBUG [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) dEAkWiMWXtw2.0.77.13 Processing NEW request: EXEC Source.native('ALTER TABLE DV_MATVIEWS_MAT_VIEW_STAGE RENAME TO DV_MATVIEWS_MAT_VIEW_TEMP')
> 15:20:00,035 DEBUG [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) dEAkWiMWXtw2.0.77.13 Obtained execution
> 15:20:00,036 DEBUG [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Source-specific command: ALTER TABLE DV_MATVIEWS_MAT_VIEW_STAGE RENAME TO DV_MATVIEWS_MAT_VIEW_TEMP
> 15:20:00,247 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=dEAkWiMWXtw2.0.77.13: org.teiid.translator.jdbc.JDBCExecutionException: 1399 TEIID11008:TEIID11004 Error executing statement(s): ALTER TABLE DV_MATVIEWS_MAT_VIEW_STAGE RENAME TO DV_MATVIEWS_MAT_VIEW_TEMP
> at org.teiid.translator.jdbc.JDBCDirectQueryExecution.execute(JDBCDirectQueryExecution.java:95) [translator-jdbc-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_102]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_102]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_102]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_102]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy81.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92)
> at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:608)
> at org.teiid.query.processor.proc.CreateCursorResultSetInstruction.process(CreateCursorResultSetInstruction.java:69)
> at org.teiid.query.processor.proc.ExecDynamicSqlInstruction$1.process(ExecDynamicSqlInstruction.java:218)
> at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:389)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:298)
> at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:270)
> at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:118)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274)
> 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:1142) [rt.jar:1.8.0_102]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_102]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102]
> Caused by: java.sql.SQLException: XAER_RMFAIL: The command cannot be executed when global transaction is in the ACTIVE state
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2713)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2663)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:888)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:730)
> at com.mysql.jdbc.jdbc2.optional.StatementWrapper.execute(StatementWrapper.java:698)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.execute(WrappedStatement.java:157)
> at org.teiid.translator.jdbc.JDBCDirectQueryExecution.execute(JDBCDirectQueryExecution.java:83) [translator-jdbc-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> ... 45 more
> 15:20:00,254 DEBUG [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) dEAkWiMWXtw2.0.77.13 Remove State
> 15:20:00,254 DEBUG [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) dEAkWiMWXtw2.0.77.13 Processing Close : EXEC Source.native('ALTER TABLE DV_MATVIEWS_MAT_VIEW_STAGE RENAME TO DV_MATVIEWS_MAT_VIEW_TEMP')
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4584) SimpleDB doesn' work
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4584?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4584:
-------------------------------------
Posted to AWS community https://forums.aws.amazon.com/thread.jspa?threadID=243224
> SimpleDB doesn' work
> --------------------
>
> Key: TEIID-4584
> URL: https://issues.jboss.org/browse/TEIID-4584
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.12.6.6_3
> Environment: RHEL 7.x, JBoss 6.4, JDV 6.3,
> JBDS 9.1.0.GA, GA-v20160414-0124-B497
> Also Fedora 23
> Reporter: Glen Wilcox
> Assignee: Steven Hawkins
>
> I was trying to set up the simpledb example:
> https://developer.jboss.org/wiki/IntegrateAmazonSimpleDBWithTeiid
> When I create the DataSource to AWS I get the following error:
> Inline image 1
> and the stack trace:
> 07:19:29,048 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 1) IJ000604: Throwable while attempting to get a new connection: null: java.lang.NoClassDefFoundError: com/amazonaws/AmazonServiceException
> at org.teiid.resource.adapter.simpledb.SimpleDBManagedConnectionFactory$1.getConnection(SimpleDBManagedConnectionFactory.java:46)
> at org.teiid.resource.adapter.simpledb.SimpleDBManagedConnectionFactory$1.getConnection(SimpleDBManagedConnectionFactory.java:41)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71) [teiid-api-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:834)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:379)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:453)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:425)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:354)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4584) SimpleDB doesn' work
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4584?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4584:
-------------------------------------
Download the JAR from here https://aws.amazon.com/sdk-for-java/ look in the zip file under "lib" directory and replace the above and see if that works
> SimpleDB doesn' work
> --------------------
>
> Key: TEIID-4584
> URL: https://issues.jboss.org/browse/TEIID-4584
> Project: Teiid
> Issue Type: Bug
> Components: Connector API
> Affects Versions: 8.12.6.6_3
> Environment: RHEL 7.x, JBoss 6.4, JDV 6.3,
> JBDS 9.1.0.GA, GA-v20160414-0124-B497
> Also Fedora 23
> Reporter: Glen Wilcox
> Assignee: Steven Hawkins
>
> I was trying to set up the simpledb example:
> https://developer.jboss.org/wiki/IntegrateAmazonSimpleDBWithTeiid
> When I create the DataSource to AWS I get the following error:
> Inline image 1
> and the stack trace:
> 07:19:29,048 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 1) IJ000604: Throwable while attempting to get a new connection: null: java.lang.NoClassDefFoundError: com/amazonaws/AmazonServiceException
> at org.teiid.resource.adapter.simpledb.SimpleDBManagedConnectionFactory$1.getConnection(SimpleDBManagedConnectionFactory.java:46)
> at org.teiid.resource.adapter.simpledb.SimpleDBManagedConnectionFactory$1.getConnection(SimpleDBManagedConnectionFactory.java:41)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71) [teiid-api-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:834)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:379)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:453)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:425)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:354)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4585) Eclipse/Designer extension to export a model project as dynamic VDBs
by Don Krapohl (JIRA)
Don Krapohl created TEIID-4585:
----------------------------------
Summary: Eclipse/Designer extension to export a model project as dynamic VDBs
Key: TEIID-4585
URL: https://issues.jboss.org/browse/TEIID-4585
Project: Teiid
Issue Type: Feature Request
Components: Tools
Reporter: Don Krapohl
Assignee: Steven Hawkins
Request is following forum ref https://developer.jboss.org/message/965470 . As a consumer we have built extensive structures in Designer (static) VDBs. We would like a tool either standalone or in Designer/Eclipse that would export a model project as proper dynamic virtual databases. Example is included in the forum.
If this tool becomes on the roadmap I will file a jira to request a feature to optimize the dynamic VDB through the use of VDB imports to eliminate redundancy in a project.
In this single project we estimate that this will save us 1 person, two 2-week sprints.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4493) Add support for integration with qgis
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4493?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4493:
---------------------------------------
[~blafond] Grammar changes:
- ARRAY[expression list] is supported for constructing an array value.
Resolver changes:
- Any numeric literal is implicitly convertible to double/float - even if there is a loss of precision.
- subqueries are allowed in just a select without a from clause
- array/row value comparisons are allowed with multiple columns projected from a subquery: (a, b) in (select x, y from foo)
I'll formally document the ARRAY syntax option and the implicit resolving change.
> Add support for integration with qgis
> --------------------------------------
>
> Key: TEIID-4493
> URL: https://issues.jboss.org/browse/TEIID-4493
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation, Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> Similar to our support for GeoServer, we should support qgis integration if possible.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (TEIID-4558) Query Plan Analyzer
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4558?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4558:
-------------------------------------
Assignee: (was: Steven Hawkins)
I'm leaving this unassigned/unbucketed for now. Our xml plan is only intended for consumption by tooling and contains a lot of information that could be presented in a different way that would highlight potential issues (which node consumed the most time, produced the most rows, etc.).
Our text form of the plan could be improved or have an alternative display to be more compact. [~kylin] had looked at that a little. I would tie any effort like this to that - make the text plan easier to read and possibly annotate things like missing cardinalities, the longest running node, etc.
> Query Plan Analyzer
> -------------------
>
> Key: TEIID-4558
> URL: https://issues.jboss.org/browse/TEIID-4558
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Affects Versions: 9.2
> Reporter: Van Halbert
>
> Provide a tool that would take a query plan and provide feed back.
> Example:
> - indicate where there maybe a problem in the structure of the query that may impact performance
> - indicate in the plan where there maybe issues (like table scan, no rows, etc.)
> - provide recommendations for improving performance
> etc..
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months