February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1010: ---------------------------------------- The fix treats unnamed Primary Keys by naming them PRIMARY_KEY. The Unique Index would therefore ALSO be unnamed, so Designer will create an index for each named UNIQUE_IDX prepended by a unique sequencial integer. In the case of the SmallA and SmallB indexes from Van's example, Designer creates: * SmallA index: UNIQUE_IDX ** Name in source:"dbo"."SmallA"."UNIQUE_IDX" * SmallB index: UNIQUE_IDX ** Name in source:"dbo"."SmallB"."UNIQUE_IDX" Note that the Name In Source holds the path reference to the corresponding target table. > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: org.teiid.designer.jdbc.relational.patch > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1609) Create DataSource dialog doesnt display when DataSources folder is selected on server view

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1609: --------------------------------------- Summary: Create DataSource dialog doesnt display when DataSources folder is selected on server view Key: TEIIDDES-1609 URL: https://issues.jboss.org/browse/TEIIDDES-1609 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 8.0 Reporter: Mark Drilling On the Servers view in Designer, the Create DataSource Dialog does not display when 'Data Sources' folder is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1591: ----------------------------------------- Assignee: Max Rydahl Andersen (was: Paul Richardson) > Improve the default eclipse dialog for entering the secure storage password > --------------------------------------------------------------------------- > > Key: TEIIDDES-1591 > URL: https://issues.jboss.org/browse/TEIIDDES-1591 > Project: Teiid Designer > Issue Type: Enhancement > Components: Eclipse Integration > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Max Rydahl Andersen > Fix For: 8.1 > > Attachments: password-provider-dialog.jpg > > > Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them! > Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1591: ------------------------------------------- Max, Could you suggest which project this could be moved to and I can create a pull request accordingly. Thanks. > Improve the default eclipse dialog for entering the secure storage password > --------------------------------------------------------------------------- > > Key: TEIIDDES-1591 > URL: https://issues.jboss.org/browse/TEIIDDES-1591 > Project: Teiid Designer > Issue Type: Enhancement > Components: Eclipse Integration > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: password-provider-dialog.jpg > > > Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them! > Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1605) Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1605. --------------------------------------- Resolution: Done > Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-1605 > URL: https://issues.jboss.org/browse/TEIIDDES-1605 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace)..... > * Opened Project > * Tried to Preview a table and got an NPE: > ** java.lang.NullPointerException > at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642) > at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > The method failing is: > private String getFullDeployedVdbName(ITeiidVdb deployedVdb) { > String fullVdbName = deployedVdb.getPropertyValue("deployment-name");; > if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) { > fullVdbName = fullVdbName + Vdb.FILE_EXTENSION; > } > return fullVdbName; > > } > ITeiidVdb is a new SPI interface. > So was the "deployment-name" property available with Teiid 7.7.x runtime? > Also can't Undeploy VDB on 7.7.2 server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-979) Add to the documentation what metadata used in designer has a material impact on runtime

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-979?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-979. ----------------------------------- Resolution: Done Added table as Appendix in 8.1 Users Guide > Add to the documentation what metadata used in designer has a material impact on runtime > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-979 > URL: https://issues.jboss.org/browse/TEIIDDES-979 > Project: Teiid Designer > Issue Type: Sub-task > Components: Documentation > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.1 > > > Add to the documentation what metadata used in designer has a material impact on runtime -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1607) org.teiid.designer.relational plugin has no Provider Name and incomplete Plugin Name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1607?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1607. ------------------------------------ Resolution: Done Completed > org.teiid.designer.relational plugin has no Provider Name and incomplete Plugin Name > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-1607 > URL: https://issues.jboss.org/browse/TEIIDDES-1607 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation, Release Work > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.1 > > > Looking at 8.1 Alpha1 Teiid Designer Feature details page, the org.teiid.designer.relational plugin... > * the Provider field is empty and should say "JBoss by Red Hat" > * Plug-in Name == Relational. Should be "Relational Plug-in" to be consistant -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1599) Add VDB resource builder to Designer build process

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1599?focusedWorklogId=12428736&p... ] Barry LaFond logged work on TEIIDDES-1599: ------------------------------------------ Author: Barry LaFond Created on: 27/Feb/13 2:25 PM Start Date: 22/Feb/13 2:23 PM Worklog Time Spent: 1 day Work Description: Added builder and warnings for any models with wrong model path in it. NEXT: Add logic to add warnings for "out of sync" models and add synchronize() call in the Quick Fix for it. Thisl will occur when source model is moved and it is imported by a view model Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 1 day Worklog Id: (was: 12428736) > Add VDB resource builder to Designer build process > -------------------------------------------------- > > Key: TEIIDDES-1599 > URL: https://issues.jboss.org/browse/TEIIDDES-1599 > Project: Teiid Designer > Issue Type: Feature Request > Components: Validation, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.1 > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > In order to help users re-synch their VDBs after model refactoring, we need to build (validate) each workspace VDB as an IResource object in order to apply/add problem markers in the workspace. > May required adding another "Builder" contribution to Designer's .project file. > The MED builder is the most recent feature that was added which could be a good model for making this happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1608) Allow any extension in the XML import wizard

by Daniel Susín (JIRA)

Daniel Susín created TEIIDDES-1608: -------------------------------------- Summary: Allow any extension in the XML import wizard Key: TEIIDDES-1608 URL: https://issues.jboss.org/browse/TEIIDDES-1608 Project: Teiid Designer Issue Type: Enhancement Components: Modeling, Usability Affects Versions: 8.0 Reporter: Daniel Susín The import XML wizard should allow optionally to select any extension besides '.xml'. Limiting it to only '.xml' prevents it from being used, for instance, to process KML files, which are perfectly compatible with the XML parsing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1569?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1569: ----------------------------------- Issue Type: Bug (was: Feature Request) > REST Extension Properties not Visible for Procedure > --------------------------------------------------- > > Key: TEIIDDES-1569 > URL: https://issues.jboss.org/browse/TEIIDDES-1569 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.0 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: org.teiid.designer.dqp.patch > > > REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2013