March 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-404) Facilitate deployment of VDB's from Designer to Teiid Server

by Barry LaFond (JIRA)

Facilitate deployment of VDB's from Designer to Teiid Server ------------------------------------------------------------ Key: TEIIDDES-404 URL: https://jira.jboss.org/jira/browse/TEIIDDES-404 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 As part of 7.0 Teiid integration, both Preview Data and VDB Execution are going to required deployment of workspace VDB's to Teiid. This can be done by Right-click VDB "Deploy to Teiid" action or DND to Teiid Server in Server/Execution View -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-176) Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs.

by Ramesh Reddy (JIRA)

Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs. ---------------------------------------------------------------------------------------------- Key: TEIIDDES-176 URL: https://jira.jboss.org/jira/browse/TEIIDDES-176 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: Ramesh Reddy Assignee: Johnny Verhaeg Priority: Critical > On Wed, 2009-05-06 at 11:35 -0400, John Doyle wrote: >> I'm throwing this idea out there with very little idea of how the >> links between Teiid and Designer function, but I think it would be >> cool and beneficial. >> >> AFAIK we don't have a user story abut how you update the version of >> Teiid that is delivered with Designer. I think that it would be >> very cool if we exposed this cabability in designer similar to the >> way Installed JREs are exposed through the Preferences page. >> Designer could come with a version of Teiid, but users could point >> Designer to other versions of Teiid installed on their system and >> choose to run with those. One of the goals we have discussed is >> that we don't want Designer to be wedded to a particular version of >> Teiid. Defining the links between to two in this manner would >> force a contract and make it easy to test and validate that >> Designer 6.X works with Teiid 6.X and 7.X, etc. >> >> What do you think? > Well that is certainly the case going forward to have such modularity, > as this has been discussed before. However, that is not case today. > There needs to be huge re-work needs to be done in designer before we > can achieve this. Currently Designer knows too much about the Teiid's > configuration, that needs to be fixed such that it only communicates > only through the known public API like JDBC and Admin API. > > Ramesh.. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature

by Dan Florian (JIRA)

The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-261 URL: https://jira.jboss.org/jira/browse/TEIIDDES-261 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Reporter: Dan Florian Fix For: 7.0 A version of Teiid Designer should be available that does not include the ability to perform data preview, connection management, and VDB execution. This design-time Designer would be suited to users that are strictly data modelers. A "design-time only" Designer would have a reduced footprint over the current Designer. Another Designer that is more suited to users that test models and VDBs would then be needed. We would build this Designer by adding on the data preview, connection management, and VDB execution capabilities to the "design-time only" Designer. Eclipse features are the way that different builds of the Designer can be accomplished. We have done a pretty good job of isolating the data preview, connection management, and VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there are a few cases of code found in "design-time only" plugins that depend on these data preview, connection management, and VDB execution plugins. These cases will have to be addressed in order to complete this task. Separate JIRAs should be written for these cases as they are found and tied to this JIRA. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-410) Merge vdb and dqp plugins

by Barry LaFond (JIRA)

Merge vdb and dqp plugins ------------------------- Key: TEIIDDES-410 URL: https://jira.jboss.org/jira/browse/TEIIDDES-410 Project: Teiid Designer Issue Type: Sub-task Reporter: Barry LaFond Due to the nature of our 7.0 changes and removal of embedded Teiid, its become more apparent we don't need the hassle of separate plugins for VDB and DQP -related code. We should investigate merging these plugins. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-235) Order of operations problem in Designer

by Mark Drilling (JIRA)

Order of operations problem in Designer --------------------------------------- Key: TEIIDDES-235 URL: https://jira.jboss.org/jira/browse/TEIIDDES-235 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 6.0.0 Reporter: Mark Drilling The following query when entered into the transformation editor: select * from dips_view.cards LEFT OUTER JOIN CramerXRefData.CardTypes ON card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE IS NULL OR card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE = device_pk is parsed as; SELECT * FROM DIPS_View.Cards LEFT OUTER JOIN CramerXRefData.CardTypes ON ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE IS NULL)) OR ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE = Device_PK)) The ordering of different variations of CompoundCriteria are not preserved correctly. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-414) Remove nested jar entries from each project's manifest

by John Verhaeg (JIRA)

Remove nested jar entries from each project's manifest ------------------------------------------------------ Key: TEIIDDES-414 URL: https://jira.jboss.org/jira/browse/TEIIDDES-414 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 6.3 Reporter: John Verhaeg Assignee: John Verhaeg Priority: Blocker Fix For: 7.0 Each project's manifest contains a reference to the jar file that was the target of the build in pre-Eclipse 3.0 days before the manifest existed and before projects were created as simple jars rather than as folders, when this was a required entry within the plugin.xml. Eclipse auto-added these entries to the manifest when we upgraded to 3.0. With the creation of jars instead of folders, we're now creating jars that contain other jars. All of these entries simple need to be removed. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-416) Combine feature and product projects into a single project.

by John Verhaeg (JIRA)

Combine feature and product projects into a single project. ----------------------------------------------------------- Key: TEIIDDES-416 URL: https://jira.jboss.org/jira/browse/TEIIDDES-416 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 6.3 Reporter: John Verhaeg Assignee: John Verhaeg Priority: Blocker Fix For: 7.0 There is no longer a need for these projects to be separate, and the new build process demands that the feature project's ID match the feature folder. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-415) Remove Ant task source from feature project

by John Verhaeg (JIRA)

Remove Ant task source from feature project ------------------------------------------- Key: TEIIDDES-415 URL: https://jira.jboss.org/jira/browse/TEIIDDES-415 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 6.3 Reporter: John Verhaeg Assignee: John Verhaeg Priority: Minor Fix For: 7.0 All of this code and the Ant library is leftover from the old build process and is obsolete. -- 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

1
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-336) SQL explorer does not always create correct template for Web services

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-336?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-336: ---------------------------------- Fix Version/s: No Future > SQL explorer does not always create correct template for Web services > --------------------------------------------------------------------- > > Key: TEIIDDES-336 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-336 > Project: Teiid Designer > Issue Type: Task > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: No Future > > Attachments: TwoItunesProjects.zip > > > The template the Designer presented to me is EXEC mytunes.tracks('xmlIn') > It should have been the full EXEC mytunes.tracks('<trackRequest><artist>artist</artist></trackRequest>' ) > I believe this has worked correctly in the past, including Milestone 1 of 5.5.3. > I've attached the two projects that are created by the iTunes test script. -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2010