October 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2135) Provide Admin API wrapper based on given AS Controller Client connection

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2135: ----------------------------------- Summary: Provide Admin API wrapper based on given AS Controller Client connection Key: TEIID-2135 URL: https://issues.jboss.org/browse/TEIID-2135 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 8.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 Currently the Admin interface is only created, when the required user name, password and host information for the AS7 is supplied. Teiid should provide an option to create this wrapper when they supply pre-built connection object -- 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

2
2
0 / 0

[JBoss JIRA] (TEIID-2083) Provide a Admin method to read the metadata of a VDB

by Ramesh Reddy (JIRA)

12 years, 1 month

3
12
0 / 0

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

by Mark Addleman (JIRA)

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (TEIID-2110) Error in Documentation: CREATE TRIGGER

by Andriy Rokhmanov (JIRA)

Andriy Rokhmanov created TEIID-2110: --------------------------------------- Summary: Error in Documentation: CREATE TRIGGER Key: TEIID-2110 URL: https://issues.jboss.org/browse/TEIID-2110 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 8.0 Reporter: Andriy Rokhmanov Assignee: Steven Hawkins Priority: Minor https://docs.jboss.org/author/display/TEIID/DDL+Metadata Section "INSTEAD OF TRIGGERS" (both Example and Diagram): Now: CREATE TRIGGER ON CustomerOrders INSTEAD OF INSERT FOR EACH ROW... Should be: CREATE TRIGGER ON CustomerOrders INSTEAD OF INSERT AS FOR EACH ROW... -- 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

3
19
0 / 0

[JBoss JIRA] (TEIID-2011) Develope a JPA Translator

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2011: ----------------------------------- Summary: Develope a JPA Translator Key: TEIID-2011 URL: https://issues.jboss.org/browse/TEIID-2011 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 Provide a JPA based translator in Teiid. The main driving force for this is to support Hibernate OGM, which in turn uses big data stores like infinispan, EhCache as backing stores. Hibernate OGM also looking to expanding to other stores like Cassendra, MongoDB etc. By providing JPA translator (think reverse hibernate), which provides - Metadata - Query API (JPQL) which makes much easier for Teiid to identify data in big data stores and gives ways to integrate with other kinds of sources, both relational and non-relational. This usecase is limited to users who has defined their data using JPA and would like to use big data stores. Additional benefit of this is to provides full Relational access to a JPA store with JDBC/ODBC and SQL. if the data in big data store is not in JPA objects, then see https://issues.jboss.org/browse/TEIID-1992 -- 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

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1280) Add parameters to procedure definition

by Steven Hawkins (JIRA)

Add parameters to procedure definition -------------------------------------- Key: TEIID-1280 URL: https://jira.jboss.org/browse/TEIID-1280 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.0 Our procedure syntax needs to add parameter definition to be independent of Designer. -- 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-2094) Projecting node issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2094: ------------------------------------- Summary: Projecting node issue Key: TEIID-2094 URL: https://issues.jboss.org/browse/TEIID-2094 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.1 If a non-pushed source node (inline view) is located over a projected node that needs to perform projection, a join node, or a select node, the resulting construction of the projection indexes will be incorrect or fail - as the input elements will not match the output elements that have been set to the views elements. -- 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
4
0 / 0

[JBoss JIRA] (TEIID-2040) Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init>

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2040: ------------------------------------ Summary: Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init> Key: TEIID-2040 URL: https://issues.jboss.org/browse/TEIID-2040 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Johnathon Lee Assignee: Steven Hawkins -- 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

2
7
0 / 0

[JBoss JIRA] (TEIID-2091) Improve transaction detection logic

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2091: ------------------------------------- Summary: Improve transaction detection logic Key: TEIID-2091 URL: https://issues.jboss.org/browse/TEIID-2091 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 The current detection logic assumes nearly all relational nodes require a transaction and does not detect special cases for access nodes. -- 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
3
0 / 0

[JBoss JIRA] (TEIID-2105) VDB Status issue with redeploys

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2105: ------------------------------------ Summary: VDB Status issue with redeploys Key: TEIID-2105 URL: https://issues.jboss.org/browse/TEIID-2105 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 8.0 Reporter: Mark Drilling Assignee: Steven Hawkins I encountered this issue via Admin API. I found that when I deployed a VDB with View DDL definition I sometimes was not able to retrieve the VDB via the Admin API getVDBs method. Steps to reproduce: 1) Deploy VDB with a valid JDBC source. works OK. 2) now, Add a View DDL defn to the VDB and redeploy it. For valid View DDL that references the JDBC source defined in 1), this works fine. However, if I submit DDL that is a valid query - but references a non-existent source group - I get the following exceptions in the log 15:57:13,993 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "MyVDB-vdb.xml" 15:57:14,026 INFO [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011907: Register module: Module "deployment.MyVDB-vdb.xml:main" from Service Module Loader 15:57:14,031 INFO [org.teiid.RUNTIME] (MSC service thread 1-5) TEIID50029 VDB MyVDB.1 model "testJDBCModel" metadata is currently being loaded. Start Time: 7/13/12 3:57 PM 15:57:14,031 INFO [org.teiid.RUNTIME] (MSC service thread 1-5) TEIID50029 VDB MyVDB.1 model "MyViewModel" metadata is currently being loaded. Start Time: 7/13/12 3:57 PM 15:57:14,056 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB MyVDB.1 model "testJDBCModel" metadata loaded. End Time: 7/13/12 3:57 PM 15:57:14,109 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB MyVDB.1 model "MyViewModel" metadata loaded. End Time: 7/13/12 3:57 PM 15:57:14,136 INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018559: Deployed "MyVDB-vdb.xml" 15:57:14,144 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31080 View MyViewModel.SFAccountBillingView validation error: QueryResolverException-Group does not exist: testSalesforceModel.Account 15:57:14,145 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31071 Invalid table; Table SFAccountBillingView has no columns defined 15:57:14,146 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40073 The metadata for the VDB MyVDB.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. 16:00:22,351 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/MyVDB] After the above submittal of view DDL that references a non-existent source - the admin.getVDBs() call doesnt return anything. Normally I'd get the VDBMetaData, make changes and redeploy. But in this case, I do not get the previously deployed VDB. -- 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

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2012