December 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1545) "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-1545: ----------------------------------------- Summary: "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows Key: TEIIDDES-1545 URL: https://issues.jboss.org/browse/TEIIDDES-1545 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.7 Environment: Windows 7 64 bit JBDS 5.0 Teiid Designer Plugin version 7.7.2.v20121025-2138-H6-GA-SOA Reporter: Debbie Steigner I have only found this issue on Windows JBDS installation. Import > "WSDL File or URL >> Source and View Model" proceed thru the wizard until you reach the "Models Definition" page, do not take the default names for Source. Try entering a name, the cursor returns to column 1 after each letter so hello becomes olleh. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-620) Add Option for Local Teiid Connection vs JNDI in WAR Generation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-620?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-620. ----------------------------------- Resolution: Rejected 1441 is completed. rejecting > Add Option for Local Teiid Connection vs JNDI in WAR Generation > --------------------------------------------------------------- > > Key: TEIIDDES-620 > URL: https://issues.jboss.org/browse/TEIIDDES-620 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.1 > > > Need to allow for a local Teiid connection in the war generation process in addition to the current JNDI connection. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-434) Input sets in XML Document model don't have access to elements in parent mapping classes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-434?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-434: ---------------------------------- Fix Version/s: Future (was: 8.1) > Input sets in XML Document model don't have access to elements in parent mapping classes > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-434 > URL: https://issues.jboss.org/browse/TEIIDDES-434 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > > Input sets in XML Document model don't have access to elements in parent mapping classes, currently > the only way something will show in any input set is if you have a mapping class and transformation at the root element. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-472) Support multi-source bindings

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-472: ---------------------------------- Fix Version/s: Future (was: 8.1) > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Fix For: Future > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-370) Designer: Allow the user to edit the preView Query before it is submitted.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-370?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-370: ---------------------------------- Fix Version/s: Future (was: 8.1) > Designer: Allow the user to edit the preView Query before it is submitted. > -------------------------------------------------------------------------- > > Key: TEIIDDES-370 > URL: https://issues.jboss.org/browse/TEIIDDES-370 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > The feature was brought up a couple times during demo of the preView Query work. Some users would like to intercept and edit the preview Query before it is submitted. This was out-of-scope for the original effort. > Maybe need more discussion here. Maybe need a dedicated "Preview Data View"... (TBD...) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-425) Add query capabilities to the Import from JDBC in the Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-425?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-425: ---------------------------------- Fix Version/s: Future (was: 8.1) > Add query capabilities to the Import from JDBC in the Designer > -------------------------------------------------------------- > > Key: TEIIDDES-425 > URL: https://issues.jboss.org/browse/TEIIDDES-425 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > Fix For: Future > > > For dealing with databases with extrremely large numbers of tables 10,000 +, it would be very helpful to have these 2 features: > 1. Search / Filter capabilities > 2. Ability to turn off the tables details on the "right" side of the dialog as retrieving that data table by table is exceedingly slow especially when dealing with 1000's of tables. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-344) Transformation editor in Designer should support comments and preserve user formatting

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-344?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-344: ---------------------------------- Fix Version/s: Future (was: 8.1) > Transformation editor in Designer should support comments and preserve user formatting > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-344 > URL: https://issues.jboss.org/browse/TEIIDDES-344 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: Future > > > We should support the ability to put comments into transformation code. This is especially useful for virtual procedures, which can get complicated, and could benefit from comments. It also comes up when bringing in SQL code from another environment (e.g. a view from Oracle) -- it would be nice to be able to preserve the comments from the original environment. > It would be nice to support comments prefixed by "--", such as in Oracle. I believe this is standard SQL-92, so we should support it as well. > ------------------- > Fix the designer transformation window, so that it actually saves what the user types (keep formatting, allow comments, etc.). This should really be one of the standard Eclipse text editing windows - MM specific stuff (other than syntax highlighting) should be decoupled from the edit window - there are a couple of requests from ING on this. > ------------------- > As Designer is treated like any other development environment and may have multiple developers working on the same project set, it is very important that comments be supported within the transformations. Although it might be helpful, it is not necessary that these comments get pushed out to source. These comments would be primarily used for developer references. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-228) Import transformation SQL fails to do anything

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-228?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-228. ----------------------------------- Resolution: Cannot Reproduce Bug See previous comment. > Import transformation SQL fails to do anything > ---------------------------------------------- > > Key: TEIIDDES-228 > URL: https://issues.jboss.org/browse/TEIIDDES-228 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.2.0 > Environment: Fedora 10, Designer 20090922 build (same thing with RC1) > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: VqtExportedTransformationSQL.txt, VqtSqlImport_ModelProjectSet.zip > > > I exported the transformation SQL from the VQT model. When I tried to import the SQL into a new VQT model, it gave the appearance it completed successfully, but none of the tables were defined. There were no errors or exceptions found in the log. Whoa... I just found a warning: Could not parse the following row: Agg3|SELECT|SELECT COUNT(*) FROM BQT1.SmallA. > The format of the exported file is not the same as that of the Metadata Text Importer, so to use that route the file must be edited. (The export version takes into account the SELECT, INSERT, UPDATE, DELETE possibilities.) BTW, this had issues as well, but that's another JIRA. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-226) Problem importing Synonyms into VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-226: ---------------------------------- Fix Version/s: Future (was: 8.1) > Problem importing Synonyms into VDB > ----------------------------------- > > Key: TEIIDDES-226 > URL: https://issues.jboss.org/browse/TEIIDDES-226 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration, VDB & Execution > Affects Versions: 6.0.0, 6.1.0, 6.2.0 > Reporter: Ram Yelamanchilli > Assignee: Mark Drilling > Priority: Minor > Labels: Designer, SYNONYM, VDB > Fix For: Future > > > I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error. > "The Base Table must reference one more more columns; there are none." > Designer version is 6.2. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1024) Create separate icons for different types of models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1024?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1024: ----------------------------------- Fix Version/s: Future (was: 8.1) > Create separate icons for different types of models > --------------------------------------------------- > > Key: TEIIDDES-1024 > URL: https://issues.jboss.org/browse/TEIIDDES-1024 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Ramesh Reddy > Priority: Minor > Fix For: Future > > > Currently the Designer only shows blue (source models), orange(view models) cubes for the models. It would be useful to show different types of icons for each model type. For example, use DB icon for Relational Database, or file icon for file based sources, xml, web-service so on. This will help identify the sources quickly when combined with names. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2012