May 2010 - teiid-designer-issues - Jboss List Archives

[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, 3 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, 3 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, 3 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

15 years, 3 months

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

15 years, 4 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

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-224) The ConfigurationInfo.def file has verbose settings for the ComponentTypes

by Ramesh Reddy (JIRA)

The ConfigurationInfo.def file has verbose settings for the ComponentTypes -------------------------------------------------------------------------- Key: TEIIDDES-224 URL: https://jira.jboss.org/jira/browse/TEIIDDES-224 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 6.1.0 Reporter: Ramesh Reddy Fix For: 6.2.0 Currently when VDB is written, the <ComponentTypes> section in the ConfigurationInfo.def file defines the component types for all the bindings defined. However the number of properties defined for each component type include all the properties in hierarchy of that Component Type. Which verbose and confusing. For example in Configuration.XML file a "Oracle Connector" defined with it's hierarchy as Oracle Connector --> JDBC Connector --> Connector where Teiid defines properties at each level, but when the def file these properties are flattened and all properties are written under component type "Oracle Connector". Looking at the issue, "ComponentType" fragment of the XML is optional, if the connector type is already in the "configuration.xml". However, designer still need to write the ComponentType information for custom connector types as that information will not be in the configuration.xml file. To determine, if a connector type is already in the "configuration.xml", the designer can check a property called "standard", if the value is "true" it can safely ignore adding the component type to the .def file. Teiid will supply the configuration.xml file with "standard" property set on all the built in types. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-243) Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage'

by Debbie Steigner (JIRA)

Request to have Root cause of connector error in designer SQL Explorer dialog instead of 'CapabilitiesMessage' -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-243 URL: https://jira.jboss.org/jira/browse/TEIIDDES-243 Project: Teiid Designer Issue Type: Feature Request Reporter: Debbie Steigner Fix For: 6.1.0 In the designer, when a connector can't start and throws an exception, it pops up a dialog that says: "Unable to create a connection for request com.metamatrix.dqp.message.CapabilitiesMessage@1cee695" However, this is not the root cause exception, so every time it happens, one must find the exception in the log and find the root cause. The root cause is often something to do with bad credentials, or an expired password, or the like. Not having this is really irritating and needlessly time-consuming. So, the feature request is to drill down in the exception stack trace to the root cause and report it's message in the dialog. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-223) Loaded Connectors dialog is empty

by Ramesh Reddy (JIRA)

Loaded Connectors dialog is empty --------------------------------- Key: TEIIDDES-223 URL: https://jira.jboss.org/jira/browse/TEIIDDES-223 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.2.0 Reporter: Ramesh Reddy I then defined my connector and dragged my model into it. That part > seems to be fine. > > Just when I go to my VDB definition, on the "Execute" page, I need to > assign a connector in order for my VDB to be able to execute. > > But I just cannot select my pre-defined connector there as the "Loaded > Connectors" tab is empty. I can define a new connector there, using the > same properties as my existing connector, but just using a different > name, and it will work fine. Loaded Bindings must have shown my previous binding to select from. -- 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, 4 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2010