June 2010 - teiid-designer-issues

[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

14 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-461) VDB Editor needs framework to display context actions for selected model entries

by Barry LaFond (JIRA)

VDB Editor needs framework to display context actions for selected model entries -------------------------------------------------------------------------------- Key: TEIIDDES-461 URL: https://jira.jboss.org/browse/TEIIDDES-461 Project: Teiid Designer Issue Type: Task Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.0 The VDB editor provides textual place-holders for translator-name and JNDI (data source) name. TEIIDDES-404 involves providing a Deploy VDB action to a desired Teiid Server instance. To facilitate this deployment, the "translator-name" and "JNDI" names have to match names of existing Translators and Data Sources on the desired server. So the VDB Editor needs to provide the hooks/actions to allow the user to "select" these items from the desired server. The VDB Editor needs to provide a context menu on selection of a row/cell in the model entry table. Upon right-click, the "fillContextMen()" call or something like that will query the SourceHandlerExtensionManager for a list of available actions which will be contributed via the VdbSourceHandler contribution in DQP plugin. Two actions will be returned to display for the user, 1) "Select Translator" and 2) "Select Data Source". Note that during these actions, the user will first have to "pick" or "connect" to a Teiid Instance. -- 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, 4 months

2
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

14 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-470) Create framework to manage data/security roles at design-time

by John Verhaeg (JIRA)

Create framework to manage data/security roles at design-time ------------------------------------------------------------- Key: TEIIDDES-470 URL: https://jira.jboss.org/browse/TEIIDDES-470 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, VDB & Execution Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Scope of roles need to be at least VDB-level, possibly project or workspace level. Roles need to automatically be imported into VDBs when VDBs are created. -- 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, 4 months

2
3
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

14 years, 4 months

2
10
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

14 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-475) Ensure support for order by null ordering

by Steve Hawkins (JIRA)

Ensure support for order by null ordering ----------------------------------------- Key: TEIIDDES-475 URL: https://jira.jboss.org/browse/TEIIDDES-475 Project: Teiid Designer Issue Type: Quality Risk Affects Versions: 7.1 Reporter: Steve Hawkins See TEIID-715. support was added for order by nulls first/last. The display node logic needs to support this as 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

14 years, 5 months

1
1
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

14 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-150) When exporting connectors, allow option to export as a CAF

by Paul Nittel (JIRA)

When exporting connectors, allow option to export as a CAF ---------------------------------------------------------- Key: TEIIDDES-150 URL: https://jira.jboss.org/jira/browse/TEIIDDES-150 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 6.0.0 Environment: fedora 10, Barry's 4/7/09 build Reporter: Paul Nittel Attachments: jbedsp-datadirect-0.0.1-SNAPSHOT.jar, ProductsXaConnector.cdk To test importing a connector, I exported one from an older Designer. In doing so, the Designer exports a .CDK file and whatever jar files the connector needs. These files are placed in the directory specified at the time of export. If we exported a Connector Archive File (CAF), all the pertinent files would be located in one easy-to-use package. -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-222) Hide "Connector Types" by default in Connector window

by Ramesh Reddy (JIRA)

Hide "Connector Types" by default in Connector window ----------------------------------------------------- Key: TEIIDDES-222 URL: https://jira.jboss.org/jira/browse/TEIIDDES-222 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 6.1.0 Reporter: Ramesh Reddy When user creates a Connector binding manually or one created automatically due to the import process, the created binding will not readily visible in the "Connectors" window, thus confuses the user. in rder to find the newly created "Connector", they need to scroll down or "hide connector types" before it can be found. It would be better the "Connector Types" are hidden by default, as they do not provide any real information by being visible. They are only required by the user during the creation of the "Connector" where they are shown anyway. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010