[JBoss JIRA] (TEIID-2431) Support partition statistics
by Van Halbert (JIRA)
Van Halbert created TEIID-2431:
----------------------------------
Summary: Support partition statistics
Key: TEIID-2431
URL: https://issues.jboss.org/browse/TEIID-2431
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.7.4
Reporter: Van Halbert
Assignee: Steven Hawkins
The stats gathering feature does not take into account of partition statistics. Most of our query hit a single partition and using the global stats is not a true indication of the statistics for the single partition. It would be nice if Teiid engine can differentiate the usage of global and partition statistics during the optimisation and planning stages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2428) Sybase15 - jconn4-26502 driver behaviour causes exception in Teiid server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2428?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2428:
----------------------------------
Fix Version/s: 8.4
> Sybase15 - jconn4-26502 driver behaviour causes exception in Teiid server
> -------------------------------------------------------------------------
>
> Key: TEIID-2428
> URL: https://issues.jboss.org/browse/TEIID-2428
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.3
> Reporter: Warren Gibson
> Assignee: Steven Hawkins
> Fix For: 8.3.1, 8.4
>
>
> If the following queries are all submitted several times against a Teiid 8.3 Beta3 server eventually the following exception will be produced and the sybase source becomes unresponsive to additional queries.
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 45, 10;
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 50, 10;
> SELECT INTKEY FROM BQT1.SmallA ORDER BY INTKEY LIMIT 55, 10;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST ROW ONLY;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST 5 ROW ONLY;
> SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY FETCH FIRST 5 ROWS ONLY;
> Further analysis by engineering (using the above queries) has revealed that with asynch processing the close of one resultset can cause a null pointer exception for a different resultset close (that's on a different connection!) This behavior was found in jconn3 and jconn4 drivers.
> Log Exception:
> 17:29:47,203 WARN [org.teiid.CONNECTOR] (Worker23_QueryProcessorQueue16357) Connector worker process failed for atomic-request=7d35ZSARrCwK.2906.1.3307: org.teiid.translator.TranslatorException: Unexpected exception while translating results: The result set is closed.
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:108)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:316) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
> Caused by: java.sql.SQLException: The result set is closed.
> at org.jboss.jca.adapters.jdbc.WrappedResultSet.checkState(WrappedResultSet.java:4081)
> at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1044)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:867)
> at org.teiid.translator.jdbc.sybase.BaseSybaseExecutionFactory.retrieveValue(BaseSybaseExecutionFactory.java:118)
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:101)
> ... 14 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2429) Large sort performance
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2429?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2429:
---------------------------------------
Another issue with the default logic is that blocked exceptions with dup remove may result in fairly large sets of the workingTuple collection staying in memory, but not being accounted for by a memory reservation.
> Large sort performance
> ----------------------
>
> Key: TEIID-2429
> URL: https://issues.jboss.org/browse/TEIID-2429
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Large sorts (high data volume over above several hundred thousand rows) experience a disproportionate performance degradation as the data set grows larger.
> This is due to the SortUtility default collection strategy that will create intermediate sort buffers too proactively.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2430) Add faster resource cleanup for failed sortutility runs
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2430:
-------------------------------------
Summary: Add faster resource cleanup for failed sortutility runs
Key: TEIID-2430
URL: https://issues.jboss.org/browse/TEIID-2430
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4
Failure during the run of sort utility (which can occur in the sort utility or outside due to blocked exceptions / streaming dup remove) will just rely on garbage collection clean-up of intermediate buffers. There should better handling in calling code to clean up proactively.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2429) Large sort performance
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2429:
-------------------------------------
Summary: Large sort performance
Key: TEIID-2429
URL: https://issues.jboss.org/browse/TEIID-2429
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4
Large sorts (high data volume over above several hundred thousand rows) experience a disproportionate performance degradation as the data set grows larger.
This is due to the SortUtility default collection strategy that will create intermediate sort buffers too proactively.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2398) Web console in domain mode loose active servers and shows just inactive ones
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2398?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2398:
--------------------------------
Fix Version/s: 8.4
(was: 8.3)
> Web console in domain mode loose active servers and shows just inactive ones
> ----------------------------------------------------------------------------
>
> Key: TEIID-2398
> URL: https://issues.jboss.org/browse/TEIID-2398
> Project: Teiid
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 8.2
> Environment: Centos 6.3, JBoss 7.1.1 TEIID 8.2, Java 1.6
> Reporter: luca gioppo
> Assignee: Ramesh Reddy
> Labels: console, domain, web
> Fix For: 8.4
>
> Attachments: teiid.png, teiid2.png, teiid3.png, teiid4.png, teiid5.png
>
>
> I have a domain environment (for now just one host with both the domain controllere and tow servers instances) with two server groups and one servre in each group; it will be configured to be in HA.
> I added the web console to the installation (copyed the stuff in the folder and hope this was the correct way of doing)
> When I go to the runtime only the stopped server are present and canno select the running one.
> This makes the console un-usable since not choosing the server stop all other activity with errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2312) Allow resource adaptor to support "security-domain"
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2312?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2312.
---------------------------------
Resolution: Done
Looking at the code, how the BinaryDispatch is created, it is already wired to take user/passwd from the subject that is passed in.
> Allow resource adaptor to support "security-domain"
> ---------------------------------------------------
>
> Key: TEIID-2312
> URL: https://issues.jboss.org/browse/TEIID-2312
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.1
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> Currently
> * LDAP
> * Salesforce
> * Google
> connectors require user-id/password for making connections with underlying systems, but I do not think they support defining the "security-domain" so that the logged-in user's credentials can be passed through to sources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2427) Include nested message in processing exception warnings
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2427?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2427:
----------------------------------
Fix Version/s: 8.3.1
(was: 8.3)
> Include nested message in processing exception warnings
> -------------------------------------------------------
>
> Key: TEIID-2427
> URL: https://issues.jboss.org/browse/TEIID-2427
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3.1
>
>
> In many instances (especially with initial non-teiid exceptions) the original intent of the exception is not clear in the warning logged by teiid because only the top level message is there (for teiid exceptions we'll typically have the code chain, but that's not necessarily useful for the user). The root message would also be helpful so that detail logging is not needed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (TEIID-2312) Allow resource adaptor to support "security-domain"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2312?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2312:
---------------------------------------
We probably also need to validate again that the cxf binary disptach is still inadequate. I don't think that has been done for as 7.x.
> Allow resource adaptor to support "security-domain"
> ---------------------------------------------------
>
> Key: TEIID-2312
> URL: https://issues.jboss.org/browse/TEIID-2312
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.1
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> Currently
> * LDAP
> * Salesforce
> * Google
> connectors require user-id/password for making connections with underlying systems, but I do not think they support defining the "security-domain" so that the logged-in user's credentials can be passed through to sources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months