August 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-167) Designer should modify workspace.properties file used by DQP to replace relative folder entries with absolute folders in the system temp folder

by Johnny Verhaeg (JIRA)

Designer should modify workspace.properties file used by DQP to replace relative folder entries with absolute folders in the system temp folder ----------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-167 URL: https://jira.jboss.org/jira/browse/TEIIDDES-167 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Affects Versions: 6.0.0 Reporter: Johnny Verhaeg The folders in the workspace.properties file in the org.teiid.dqp project are currently being created in the Eclipse installation folder at runtime; i.e., they are not even relative to the workspace. This file is read directly by Teiid Embedded, so to correct this issue, we should load the properties, modify the folder entries to be absolute entries within the system temp folder, and save them before handing the URL of the file to Teiid Embedded in dqp.ui.QueryClient.buildConnectionURL(). -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-199) Add versioning info to the generated modelextensions.

by John Doyle (JIRA)

Add versioning info to the generated modelextensions. ----------------------------------------------------- Key: TEIIDDES-199 URL: https://jira.jboss.org/jira/browse/TEIIDDES-199 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.1.0 The model extension should have a version number so that change can be accounted for in later versions. -- 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

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-214) Validate that the jdbc4olap driver works as expected in Designer and Teiid.

by John Doyle (JIRA)

Validate that the jdbc4olap driver works as expected in Designer and Teiid. --------------------------------------------------------------------------- Key: TEIIDDES-214 URL: https://jira.jboss.org/jira/browse/TEIIDDES-214 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: John Doyle Assignee: John Doyle http://www.jdbc4olap.org/ provides a type 4 JDBC driver for OLAP sources that support XMLA. Supporting this driver will provide access to many OLAP sources (SAP, Microsoft, Mondrian) Currently the only OLAP source that we have tested with is SAP BW via the OLAP BAPI interface. Those BAPIs are procedural and require the model designer to create extensive procedural logic in their models. jdbc4olap should enable a user to access OLAP data via standard JDBC semantics. -- 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

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-198) Error in TestServerRuntimeMetadata unit test

by Barry LaFond (JIRA)

Error in TestServerRuntimeMetadata unit test -------------------------------------------- Key: TEIIDDES-198 URL: https://jira.jboss.org/jira/browse/TEIIDDES-198 Project: Teiid Designer Issue Type: Bug Reporter: Barry LaFond Fix For: 6.1.1 Error in TestServerRuntimeMetadata.testGetXmlSchemas() method. Appears that the TreeMappingRootSqlAspect.getTransformationInfo() method is calling toUpperCase() on the Import locations. This results in an XSD file potentially having Case Sensitivity problems on LINUX, in this case. Need to investigate removing this toUpperCase() call. This has not manifested itself because it's a runtime/server thing and only happens if the XML validation is turned on which is basically not done. Our unit test happens to test ALL the basic methods and we haven't run unit tests consistently on LINUX until recently with 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

14 years, 2 months

1
3
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, 5 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, 5 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, 5 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

14 years, 5 months

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

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-200) Source Model Not Added To VDB Execution Page Of VDB Editor

by Dan Florian (JIRA)

Source Model Not Added To VDB Execution Page Of VDB Editor ---------------------------------------------------------- Key: TEIIDDES-200 URL: https://jira.jboss.org/jira/browse/TEIIDDES-200 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.1.0 Environment: Ubuntu 8.04 Reporter: Dan Florian Fix For: Future Attachments: BookSetMixed.zip Add BooksDoc to the VDB then go to the Execution tab. This shows in the log: Unable to resolve reference to a resource with the URI file:/home/dflorian/Runtime-Workspaces/.metadata/.plugins/org.teiid.designer.vdb.edit/vdbWorkingFolder/1243886654886_6290397909764948307/Book%20Set%20Mixed/BookDatatypes.xsd Notice that Books.xmi is NOT added but BooksSS.xmi is added. If you add Books.xmi by itself it DOES getting added OK. Added model project set as an attachment. -- 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, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2009