April 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-259) UDF model file needs to bundled with VDB

by Ramesh Reddy (JIRA)

UDF model file needs to bundled with VDB ---------------------------------------- Key: TEIIDDES-259 URL: https://jira.jboss.org/jira/browse/TEIIDDES-259 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Reporter: Ramesh Reddy Currently (<6.3) the UDF model (FunctionDefinitions.xmi) file is supplied to Teiid Runtime separately. Starting with 7.0 release this file will be only accepted if it is bundled inside the VDB artifact. Designer needs to be modified to bundle this file inside the 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

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-409) Re-implement Preview Data functionality

by Barry LaFond (JIRA)

Re-implement Preview Data functionality --------------------------------------- Key: TEIIDDES-409 URL: https://jira.jboss.org/jira/browse/TEIIDDES-409 Project: Teiid Designer Issue Type: Sub-task Components: Data Preview, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Because of removal of Teiid Embedded, Data Preview will have to be done a different way. Plan is to create a hidden VDB with applicable/dependent models and hot-deploy to Teiid for Execution. This JIRA covers all work targeted to replace this functionality. -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-401) Adapt VDB definition and management to 7.0 Teiid JCA Connector, UDF and Roles framework

by Barry LaFond (JIRA)

Adapt VDB definition and management to 7.0 Teiid JCA Connector, UDF and Roles framework --------------------------------------------------------------------------------------- Key: TEIIDDES-401 URL: https://jira.jboss.org/jira/browse/TEIIDDES-401 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Adapt VDB definition and management to be compatible with connector, roles and UDF delivery to Teiid. - Adapt VDB manifest new VDB XSD schema - Combine ConfigurationInfo.def and MetaMatrix-VdbManifestModel.xmi into one XML file - Add feature to include UDF model in VDB - Replace VDB read/write via EMF (xmi) with custom read/write (xml). Maintain in-memory EMF VDB classes - Do NOT include "MetaMatrixDataServices.wsdl". This will not be supported by Teiid. -- 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, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (TEIIDDES-255) Teiid embedded 7.0 integration

by Barry LaFond (JIRA)

Teiid embedded 7.0 integration ------------------------------ Key: TEIIDDES-255 URL: https://jira.jboss.org/jira/browse/TEIIDDES-255 Project: Teiid Designer Issue Type: Task Components: Teiid Integration Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.0 Initiate 7.0 Teiid Designer plugin updates and integrate initial 7.0 Teiid embedded milestone into Teiid Designer. -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-413) Move auto-creation of connector bindings during JDBC import to occur during Preview Data Action or VDB Editor connector management framework.

by Barry LaFond (JIRA)

Move auto-creation of connector bindings during JDBC import to occur during Preview Data Action or VDB Editor connector management framework. --------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-413 URL: https://jira.jboss.org/jira/browse/TEIIDDES-413 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 Since connectors are tied to specific servers and a workspace can have connections to multiple Teiid servers, the user is going to have to assist in auto-creation of connectors and binding models to the new connectors. This should be moved to the Preview Data action framework where the same logic is applied, however, the element of selecting a Teiid Server is required. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-265) Reimplement binding creation for the WSDL to Relational importer around new admin API.

by John Doyle (JIRA)

Reimplement binding creation for the WSDL to Relational importer around new admin API. -------------------------------------------------------------------------------------- Key: TEIIDDES-265 URL: https://jira.jboss.org/jira/browse/TEIIDDES-265 Project: Teiid Designer Issue Type: Task Components: Import/Export Affects Versions: 7.0 Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Recreate the binding creation code when the new Teiid admin API is integrated. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-267) UDF-related changes

by Barry LaFond (JIRA)

UDF-related changes ------------------- Key: TEIIDDES-267 URL: https://jira.jboss.org/jira/browse/TEIIDDES-267 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.0 Teiid 7.0 has changed their UDF-related code requiring re-integrating their new framework into Designer. FunctionLibraryManager doesn't exist anymore, FunctionLibrary has changed. 1) Investigate changes to Teiid and how Designer is supposed to handle UDF models in workspace. -- 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, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-406) Design Time Role Management

by Barry LaFond (JIRA)

Design Time Role Management --------------------------- Key: TEIIDDES-406 URL: https://jira.jboss.org/jira/browse/TEIIDDES-406 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 Role management in "Metamatrix" days was done via it's console. Today, JOPR/JON provides the console-type functionality. However, the data-role management is being pushed down to design-time. So Designer needs to take this on, allow data roles (authorization/entitlements) at the column, table and model levels. In addition there needs to be a way to manage higher-level "security" roles that will be mapped to actual roles when VDB's are deployed to the server. This will required injecting these roles into the VDB for transport and eventual mapping. -- 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, 2 months

1
4
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, 2 months

2
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-211) Create an Action to generate the XML-R extensions for am existing relational model.

by John Doyle (JIRA)

Create an Action to generate the XML-R extensions for am existing relational model. ----------------------------------------------------------------------------------- Key: TEIIDDES-211 URL: https://jira.jboss.org/jira/browse/TEIIDDES-211 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.1.0, 6.1.1 Reporter: John Doyle Fix For: Future An implication of the way we now generate extension models is that a user cannot manually model am XML source. There is no way to create the model extensions except to manually generate them as well. An Action off of the modeling menu to create the appropriate extension would resolve this. -- 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, 3 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2010