October 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-217) JDBC Import Error from MySQL with BIT datatypes

by Mark Drilling (JIRA)

JDBC Import Error from MySQL with BIT datatypes ----------------------------------------------- Key: TEIIDDES-217 URL: https://jira.jboss.org/jira/browse/TEIIDDES-217 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Barry LaFond Priority: Minor JDBC import from a MySQL database having columns of BIT datatype fails. The import succeeds, but attempts to re-open the generated relational model fail. Further inspection of the .xmi shows that an incorrect 'defaultValue' for the column has been written to the xmi model file. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-178) Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/

by Warren Gibson (JIRA)

Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/ -------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-178 URL: https://jira.jboss.org/jira/browse/TEIIDDES-178 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Windows XP Client Reporter: Warren Gibson Priority: Minor I had downloaded Eclipse 3.4.1 and installed it as a fresh install. I got teiid_designer_6.0.0.v20090430 from SVN. The designer zip file was on my desktop. I took the normal steps to install designer. When it installed I got the following. This seems to happen with every install on the Windows client. Not sure if it is a defect or is related to the designer zip being on my desktop. Error initializing mirrors for: jar:file:C:\Documents and Settings\admindv.SLNTQM13\Desktop\teiid_designer_6.0.0.v20090430.zip!/ java.net.URISyntaxException: Relative path in absolute URI: jar://file:C:%5CDocuments%20and%20Settings%5Cadmindv.SLNTQM13%5CDesktop%5Cteiid_designer_6.0.0.v20090430.zip!/ at java.net.URI.checkPath(Unknown Source) at java.net.URI.<init>(Unknown Source) at org.eclipse.equinox.internal.p2.core.helpers.URLUtil.toURI(URLUtil.java:65) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorSelector.<init>(MirrorSelector.java:106) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getMirror(SimpleArtifactRepository.java:490) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:447) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:515) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:162) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:146) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:94) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:504) at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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, 2 months

2
2
0 / 0

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

13 years, 6 months

1
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

13 years, 8 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

13 years, 9 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

13 years, 9 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

13 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2009