September 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2139) CLONE - Factor out common table expressions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2139: ------------------------------------- Summary: CLONE - Factor out common table expressions Key: TEIID-2139 URL: https://issues.jboss.org/browse/TEIID-2139 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Mark Addleman Assignee: Steven Hawkins Fix For: 8.2 Query planner should factor out common table expressions within queries so they are only executed once. See https://community.jboss.org/message/742355 for more context. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-1543) Add a query hint to limit the number of concurrent source queries

by Steven Hawkins (JIRA)

Add a query hint to limit the number of concurrent source queries ----------------------------------------------------------------- Key: TEIID-1543 URL: https://issues.jboss.org/browse/TEIID-1543 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins We would like a new query hint to limit the number of parallel executions of union members. This is useful in two situations: 1. When the queries are expensive, but the overall union contains a limit that is most likely to be fulfilled by the first member of the union 2. When the queries are backed by a common resource which may be overloaded by multiple queries The addition of a hint would make this manageable by the client; perhaps something like "/*+ parallel=2*/"? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic

by Steve Hawkins (JIRA)

Reuse dynamic sql plans and allow for prepared statements in procedure logic ---------------------------------------------------------------------------- Key: TEIID-1226 URL: https://jira.jboss.org/browse/TEIID-1226 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 8.0 Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse. Also procedure logic should have a mechanism to execute prepared statements for further plan reuse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (TEIID-2132) Teiid 8.0 API does not expose boundport in Mbean attribute for Teiid-JDBC

by Akshay Harale (JIRA)

Akshay Harale created TEIID-2132: ------------------------------------ Summary: Teiid 8.0 API does not expose boundport in Mbean attribute for Teiid-JDBC Key: TEIID-2132 URL: https://issues.jboss.org/browse/TEIID-2132 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Environment: jboss 7, teiid 8, windows 7 Reporter: Akshay Harale Assignee: Steven Hawkins Priority: Minor When offset is set for jboss from standalone.xml or standalone.conf.bat file, the bound port is not displyed in MBean server. For example, <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:25}"> In above line if I set the value as 25 then that should be added to the default socket port values and exposed as bound port value in MBean server. But in case of teiid the "teiid-jdbc" 's boundPort value is not exposed by the jboss. All other boundPorts values are correctly shown in Mbean, except teiid-jdbc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
3
0 / 0

[JBoss JIRA] (TEIID-1979) The RAR should be unbundled when packaged in the jboss kit

by Van Halbert (JIRA)

Van Halbert created TEIID-1979: ---------------------------------- Summary: The RAR should be unbundled when packaged in the jboss kit Key: TEIID-1979 URL: https://issues.jboss.org/browse/TEIID-1979 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 8.0 The RAR file should be unbundled, instead of zipped up, when it is packaged in the jboss kit. This change is being pushed up stream. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
11
0 / 0

[JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2035: ----------------------------------- Summary: DeleteDataSource method on Admin API does not completely delete the Connection Factory Key: TEIID-2035 URL: https://issues.jboss.org/browse/TEIID-2035 Project: Teiid Issue Type: Bug Reporter: Ramesh Reddy Assignee: Ramesh Reddy ConnectionFactory requires a two step creation process 1) create the resource-adaptor section 2) connection factory section The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-1248) Clob usability

by Steven Hawkins (JIRA)

Clob usability -------------- Key: TEIID-1248 URL: https://jira.jboss.org/browse/TEIID-1248 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 8.0 In many circumstances, clobs should be treated as charsequences to allow for use in string functions (concat returning clob, insert, left, etc.). There have also been customer requests to treat clobs as comparable, but that there are a lot of places including at design time where we validate against clobs being comparable that it may not be a good idea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1700) Move odbc cursor logic to engine

by Steven Hawkins (JIRA)

Move odbc cursor logic to engine -------------------------------- Key: TEIID-1700 URL: https://issues.jboss.org/browse/TEIID-1700 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 ODBC added support for declared cursors, which would be a good general/procedure language feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
9
0 / 0

[JBoss JIRA] (TEIID-2085) Additional feature to TEIID-1726

by Debbie Steigner (JIRA)

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2223: ---------------------------------- Summary: Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script Key: TEIID-2223 URL: https://issues.jboss.org/browse/TEIID-2223 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.7.2 Reporter: Paul Nittel Assignee: Steven Hawkins This is a weird case. If I deploy a dynamic VDB from a compiled Groovy script, it is not seen as ACTIVE by the script. The server log shows it is active. If I use a non-compiled Groovy script, it all works fine. To add to the intrigue, if the compiled script periodically polls to see if the VDB is active, and I go to the Virtual Databases display in RHQ, the script magically sees the VDB as ACTIVE. I'm attaching the materials used in this test. -- 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

12 years, 2 months

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2012