August 2010 - teiid-designer-issues

[JBoss JIRA] Closed: (TEIIDDES-269) Import DDL

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-269?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-269. --------------------------------- > Import DDL > ---------- > > Key: TEIIDDES-269 > URL: https://jira.jboss.org/browse/TEIIDDES-269 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Marc Shirley > Assignee: John Verhaeg > Fix For: 7.1 > > > Just need to make sure we do it really well -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-335) declare with a subquery assignment formats poorly

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-335?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-335. --------------------------------- > declare with a subquery assignment formats poorly > ------------------------------------------------- > > Key: TEIIDDES-335 > URL: https://jira.jboss.org/browse/TEIIDDES-335 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Optional > Fix For: 7.1 > > > In a virtual procedure the formating of a declare with a subquery will look like: > create ... > begin > declare string x = select ... > from > .... > where > ..... > The "from" and the "where" keywords are no indentation at all. -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-450) Implement the concept of a Translator into Teiid Designer

by Barry LaFond (JIRA)

Implement the concept of a Translator into Teiid Designer --------------------------------------------------------- Key: TEIIDDES-450 URL: https://jira.jboss.org/browse/TEIIDDES-450 Project: Teiid Designer Issue Type: Task Components: Editors, Teiid Integration, VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 The Teiid Project has refactored their connection framework to better align their methodology with the AS container and the JON/JOPR community. As a result Designer will change it's connection framework from dealing with Connectors and Connector Types (ala MMX & Teiid Designer 6.0 thru 6.3). In it's place will be the concepts of Translators and Data Sources. The Translators hold the Teiid-specific properties and methods used at run-time to "translate" or transform/adjust any user query through the Teiid engine at run-time. This takes the place of actual Teiid-specific connector type properties. Data Sources are the portion of "Connecton Factories" that only deal with the actual data source connection properties (URL, Username, pwd, Driver class, etc.....) Designer needs to work on modifying the following: 1) Adjusting the "Teiid" View and underlying ExecutionAdmin (aka Connectors View) to display Translators and their instances instead of "Connector Types and their Connector instances". 2) Provide the hooks in the VDB Editor to manage both a "translator-name" and "connection-jndi-name" within each Relational Source Model's "source" element properties. 3) Provide the hooks for auto-binding models to Translators and JNDI Data Sources to simplify Preview Data functionality. 4) Provide the hooks for allowing users to "edit" or "override" any Translator property for each Relational Source model in a VDB. 5) Provide the hooks to search, select and re-use any set of Translator Properties that may exist in any VDB in the Designer workspace. -- 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

15 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-564) Preview from Procedure fails: number of bound values '0' does not match number of parameters '1' in prepared statement.

by Paul Nittel (JIRA)

Preview from Procedure fails: number of bound values '0' does not match number of parameters '1' in prepared statement. ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-564 URL: https://jira.jboss.org/browse/TEIIDDES-564 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1 Environment: TeiidDesigner 7.1M2, Teiid 7.1 Final Reporter: Paul Nittel Attachments: ProcedureParameters.zip I created a small procedure which requires a single input parameter. When previewed, I receive the error noted in the title. If I deploy the VDB to the Teiid server, the same procedure executes OK. (Hence my logging it against the Designer.) Here is the exception from the server.log: [QueryResolverException]The number of bound values '0' does not match the number of parameters '1' in the prepared statement. at org.teiid.dqp.internal.process.PreparedStatementRequest.resolveParameterValues(PreparedStatementRequest.java:262) at org.teiid.dqp.internal.process.PreparedStatementRequest.generatePlan(PreparedStatementRequest.java:167) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:437) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:352) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:174) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) 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) Here is the transformation SQL: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM Parts_Oracle.PARTS WHERE VPARTS.NEWPROCEDURE.colorIN LIKE Parts_Oracle.PARTS.PART_COLOR; END I queried using the color 'Red'. Model Project Set will be attached. -- 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

15 years, 8 months

2
7
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-296) XSD to Relational importer fails on simple schema import.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-296?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-296. --------------------------------- > XSD to Relational importer fails on simple schema import. > --------------------------------------------------------- > > Key: TEIIDDES-296 > URL: https://jira.jboss.org/browse/TEIIDDES-296 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Environment: Linux Designer on RHEL-CSB > Reporter: John Doyle > Assignee: John Doyle > Fix For: 7.1 > > Attachments: XSDImportFailure.zip > > > Use the XML Schema as relational source model importer on pos.xsd in the attached model set. It produces this exception when generating the model. > java.lang.NullPointerException > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicSet(BasicEObjectImpl.java:558) > at com.metamatrix.modeler.internal.core.ObjectExtension.eDynamicSet(ObjectExtension.java:90) > at com.metamatrix.modeler.modelgenerator.xml.modelextension.impl.BaseXMLRelationalExtensionManagerImpl.setNamespacePrefixesAttribute(BaseXMLRelationalExtensionManagerImpl.java:38) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNamespacePrefixesAttribute(XmlSchemaAsRelationalModelProcessor.java:327) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setTableNamespacePrefixes(XmlSchemaAsRelationalModelProcessor.java:273) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewTable(XmlSchemaAsRelationalModelProcessor.java:96) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewEntity(XmlSchemaAsRelationalModelProcessor.java:75) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNameAndNameInSource(XmlSchemaAsRelationalModelProcessor.java:65) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1058) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:804) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:326) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:547) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:587) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:333) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:311) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.modelgenerator.xml.wizards.XsdAsRelationalImportWizard$1.run(XsdAsRelationalImportWizard.java:504) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- 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

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-509) Create Action to generate SalesForce function definitions

by John Doyle (JIRA)

Create Action to generate SalesForce function definitions --------------------------------------------------------- Key: TEIIDDES-509 URL: https://jira.jboss.org/browse/TEIIDDES-509 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 The way UDFs are managed is changing in Teiid 7.1, and the way the SF functions are delivered has to change. An Eclipse Action needs to be created that puts the function definitions in a model project. The Action should be launchable directly by a user, an perhaps the importer could be smartened up to trigger the creation if the model contains multiselect column types. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-575) Remove the UUID prefix progress monitor labels during Preview Data set-up.

by Barry LaFond (JIRA)

Remove the UUID prefix progress monitor labels during Preview Data set-up. -------------------------------------------------------------------------- Key: TEIIDDES-575 URL: https://jira.jboss.org/browse/TEIIDDES-575 Project: Teiid Designer Issue Type: Bug Components: Data Preview Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.1 Preview Data feature requires setup which includes deploying required single-model preview VDS's to a default server. Right now, their names are prefixed with a hideous UUID and show up in the Progress Monitor. Would be really nice to only show the Model name (including path) to the user while this work is being performed. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-501) Remove the workaround created for TEIIDDES-500

by John Doyle (JIRA)

Remove the workaround created for TEIIDDES-500 ---------------------------------------------- Key: TEIIDDES-501 URL: https://jira.jboss.org/browse/TEIIDDES-501 Project: Teiid Designer Issue Type: Task Components: Eclipse Integration Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 TEIIDDES-500 required a workaround for TEIID-1141. When the fix for 1141 is pulled into designer, the workaround should be removed. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-227) Errors when importing procedures from relational (Oracle) source

by Paul Nittel (JIRA)

Errors when importing procedures from relational (Oracle) source ---------------------------------------------------------------- Key: TEIIDDES-227 URL: https://jira.jboss.org/jira/browse/TEIIDDES-227 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.2.0 Environment: fedora 10, Designer 6.2 RC1 Reporter: Paul Nittel I tried to import the procedures from the Oracle 10g BQT source and ran into a set of problems. 1 - At the end of the import, a dialog is shown that proclaims the import failed (Unabled to import model into workspace. See log for details). Yes, it does say, "Unabled." In the log file there was this NPE: !ENTRY org.teiid.designer.jdbc.relational 4 3003 2009-09-22 07:52:50.914 !MESSAGE Import resulted in 1 errors !SUBENTRY 1 org.teiid.designer.jdbc.relational 4 0 2009-09-22 07:52:50.914 !MESSAGE Unexpected exception while creating relational model from BQT O11 !STACK 0 java.lang.NullPointerException at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:274) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2441) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createParameters(RelationalModelProcessorImpl.java:2192) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1129) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:816) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:336) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:541) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:584) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:343) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:319) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:309) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:677) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:262) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.teiid.designer.compare 0 60002 2009-09-22 07:52:50.914 !MESSAGE Merging completed 2 - I tried a different approach where I imported tables and then imported (update) to get the procedures. I deselected all procedures and added these: SP_ALL_SMALLA_ROWS, SP_COUNTSMALLA, SP_COUNT_ALL_SMALLA_ROWS, SP_COUNT_ROWS_BETWEEN, and SP_ROWS_BETWEEN. The result was no tables and only the name of the SP_ALL_SMALLA_ROWS procedure (no actual procedure). The Review Updates panel of the wizard shows only one new entry: SP_ALL_SMALLA_ROWS. Clicking Finish produces the error. -- 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

15 years, 8 months

2
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-560) Materialized view with no target table set has inappropriate warning

by Steve Hawkins (JIRA)

Materialized view with no target table set has inappropriate warning -------------------------------------------------------------------- Key: TEIIDDES-560 URL: https://jira.jboss.org/browse/TEIIDDES-560 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Reporter: Steve Hawkins When using materialization, not setting a target table will use the internal materialization logic. The current Designer warning indicates that materialization will not be used. It should either say that internal materialization will be used, or not be a warning at all. -- 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

15 years, 8 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010