June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1013) Load the UDF based on the information provided in the vdb.xml

by Ramesh Reddy (JIRA)

Load the UDF based on the information provided in the vdb.xml ------------------------------------------------------------- Key: TEIID-1013 URL: https://jira.jboss.org/jira/browse/TEIID-1013 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 With the new "vdb.xml" the UDF files will be defined as "FUNCTION" models inside it. The actual physical files will be included inside the VDB. The VDB deployer needs to be modified to load the UDF files. Note that there can be more then single UDF file inside a VDB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1130) NPE when using exportVDB from adminshell

by Paul Nittel (JIRA)

NPE when using exportVDB from adminshell ---------------------------------------- Key: TEIID-1130 URL: https://jira.jboss.org/browse/TEIID-1130 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.0 Environment: Fedora 12, Teiid 7 CR2 Reporter: Paul Nittel Assignee: Steve Hawkins After deploying a VDB, I tried to export it and received an NPE. groovy:000> getVDBs() ===> [one.1[Parts_MySQL[Parts_MySQL/mysql/9cc74d93-435a-4b64-b81b-2e1f42ee15fb__monday_Parts_MySQL], SYS[SYS/SYS/SYS]], two.1[Parts_Oracle[Parts_Oracle/oracle/7fd04942-83de-4a84-a916-de398455e491__m1_Parts_Oracle], Parts_MySQL[Parts_MySQL/mysql/7fd04942-83de-4a84-a916-de398455e491__m1_Parts_MySQL], SYS[SYS/SYS/SYS]]] groovy:000> exportVDB("two",1,"two_v1.vdb") ERROR java.lang.NullPointerException: null at org.teiid.core.util.ObjectConverterUtil.write (ObjectConverterUtil.java:173) at org.teiid.core.util.ObjectConverterUtil.write (ObjectConverterUtil.java:158) at org.teiid.adminshell.AdminShell.writeFile (AdminShell.java:310) at org.teiid.adminshell.AdminShell.exportVDB (AdminShell.java:319) at org.teiid.adminshell.AdminShell$exportVDB.callStatic (Unknown Source) at groovysh_evaluate.run (groovysh_evaluate:3) -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1124) Confusion with "java:" prefix in the DataSource from tooling

by Ramesh Reddy (JIRA)

Confusion with "java:" prefix in the DataSource from tooling ------------------------------------------------------------ Key: TEIID-1124 URL: https://jira.jboss.org/browse/TEIID-1124 Project: Teiid Issue Type: Task Components: AdminApi, Server Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 There is confusion from the tooling side with automatic addition of the "java:" prefix to the data source name created. Currently in the Admin API there are 3 methods correspond to data sources 1) createDataSource 2) deleteDataSource 3) getDataSourceNames Ideally all the methods should be using the consistent names. However, if the names retrieved from the "getDataSourceNames" used as the JNDI names that will not work in Teiid runtime as they do have "java:". If the method returns the names with "java:", the the "delete" will not work and inconsistent with "create" call. The problem is management object used in the Admin API and data source object have different discovery names. Here we could solve by providing another method called "getDataSourceJNDINames" that has the "java:" prefix on its names, but it will further add to the confusion. Even though not ideal, it may be OK and less confusing to resolve the data source name inside the Teiid engine by automatically adding the "java:" prefix, if the name does not already contain this prefix. If the data source is not found with prefix, then Teiid can retry lookup using the original name. Thus it will work both ways. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-36) XAConnection needs to notify when it is no longer valid

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-36?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins closed TEIID-36. ------------------------------ > XAConnection needs to notify when it is no longer valid > ------------------------------------------------------- > > Key: TEIID-36 > URL: https://jira.jboss.org/browse/TEIID-36 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.0 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The XAConnection does not properly notify listeners when the connection has become invalid. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1098) Add Long Running Query Limit Property to Teiid Engine Managed Component

by Ted Jones (JIRA)

Add Long Running Query Limit Property to Teiid Engine Managed Component ----------------------------------------------------------------------- Key: TEIID-1098 URL: https://jira.jboss.org/browse/TEIID-1098 Project: Teiid Issue Type: Task Components: Server Affects Versions: 6.2.0 Reporter: Ted Jones Assignee: Steve Hawkins Fix For: 7.0 We need a way to persist the long running query limit value for use in the Teiid Jopr plugin metrics and operations. If this property were added to the engine with a default value of 600 milliseconds, we'd be in like that there. -- 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Closed: (TEIID-980) Add ability to apply XSLT stylesheets at the datasource level

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-980?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-980. ------------------------------- > Add ability to apply XSLT stylesheets at the datasource level > ------------------------------------------------------------- > > Key: TEIID-980 > URL: https://jira.jboss.org/browse/TEIID-980 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Reporter: Marc Shirley > Fix For: 7.0 > > > XML data source contains a varying unknown number of "word" elements inside a "segment" that they wish to convert to a single string on the data source side. XQuery did not meet their needs and trying to do a concat fails due to the unknown number of elements. They would like to be able to apply the stylesheet before querying against the file to be able to retrieve a single paragraph, rather than attempt to piece together an unknown number of elements. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1026) Refine plan/annotation logic

by Steven Hawkins (JIRA)

Refine plan/annotation logic ---------------------------- Key: TEIID-1026 URL: https://jira.jboss.org/jira/browse/TEIID-1026 Project: Teiid Issue Type: Task Components: JDBC Driver, Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 The annotation and plan debug logic should be used more pervasively in the query engine. Also the client plannode and annotation classes should be used in the engine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Closed: (TEIID-199) Integration with JBoss Identity project

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-199?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-199. ------------------------------- > Integration with JBoss Identity project > --------------------------------------- > > Key: TEIID-199 > URL: https://jira.jboss.org/browse/TEIID-199 > Project: Teiid > Issue Type: Sub-task > Components: Server > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: Steven Hawkins > Fix For: 7.0 > > > There is a project underway, JBoss Identity (https://jira.jboss.org/jira/browse/JBID), that aims to provide common identity management support across many JBoss projects/products. According to the project leader's blog (http://anil-identity.blogspot.com/2008/12/federated-identity-support-with...), JBoss Application Server, JBoss Portal, JBoss SOA, JBoss Rules/Drools, and JBoss Seam are all on board with this approach. We should see if it makes sense for us to jump on the bandwagon. > The end goal of using the JBoss Identity stuff would be to replace the custom membership domain provider for authentication, and also to leverage it to provide SAML-based authorization for (ideally fine grained) access to Federate virtual databases. > SAML-based authorization has been a frequent request by prospects/customers for the closed source MetaMatrix product that is an ancestor to Federate. > I'm deliberately logging this one in the Federate project rather than the JBEDSP product JIRA since JBoss Identity itself is also still in project-only status. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1126) Web Service VDB Execution Error

by Ted Jones (JIRA)

Web Service VDB Execution Error ------------------------------- Key: TEIID-1126 URL: https://jira.jboss.org/browse/TEIID-1126 Project: Teiid Issue Type: Bug Components: Query Engine, XML Planner/Processor Affects Versions: 7.0 Reporter: Ted Jones Assignee: Steve Hawkins Fix For: 7.0 Executing a stored procedure for a web service model (exec Books_MySql_WS.Books_MySql_BOOKS.getBOOKS()), I receive the following exception: 14:56:53,033 ERROR [PROCESSOR] Unexpected exception for request IvKjO3sOrdrZ.0 [TeiidComponentException]Error trying to read schemas for the document/table : Books_MySql_Output_View.BOOKS_OutputView at org.teiid.metadata.TransformationMetadata.getXMLSchemas(TransformationMetadata.java:771) at org.teiid.query.metadata.TempMetadataAdapter.getXMLSchemas(TempMetadataAdapter.java:489) at org.teiid.query.metadata.TempMetadataAdapter.getXMLSchemas(TempMetadataAdapter.java:489) at org.teiid.query.metadata.TempMetadataAdapter.getXMLSchemas(TempMetadataAdapter.java:489) at org.teiid.query.optimizer.xml.XMLPlanner.preparePlan(XMLPlanner.java:137) at org.teiid.query.optimizer.xml.XMLPlanner.optimize(XMLPlanner.java:85) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:104) at org.teiid.query.optimizer.proc.ProcedurePlanner.optimize(ProcedurePlanner.java:106) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:98) at org.teiid.query.optimizer.relational.RelationalPlanner.addNestedCommand(RelationalPlanner.java:749) at org.teiid.query.optimizer.relational.RelationalPlanner.addNestedProcedure(RelationalPlanner.java:486) at org.teiid.query.optimizer.relational.RelationalPlanner.createStoredProcedurePlan(RelationalPlanner.java:501) at org.teiid.query.optimizer.relational.RelationalPlanner.generatePlan(RelationalPlanner.java:406) at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:146) at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:106) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:427) at org.teiid.dqp.internal.process.PreparedStatementRequest.generatePlan(PreparedStatementRequest.java:143) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:450) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:349) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:167) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:190) at org.teiid.dqp.internal.process.DQPWorkContext$2.call(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:176) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:187) at org.teiid.dqp.internal.process.StatsCapturingWorkManager$WorkWrapper.run(StatsCapturingWorkManager.java:102) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- 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

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Closed: (TEIID-171) Add SQL/XML support

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-171?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-171. ------------------------------- > Add SQL/XML support > ------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > We should add basic SQL./XML support to both create documents and extract rows from documents -- 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

14 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010