December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2032) Add validation to "VDB JNDI Name" field in "Create Web service WAR File" dialog

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2032?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2032. ---------------------------------- Resolution: Out of Date > Add validation to "VDB JNDI Name" field in "Create Web service WAR File" dialog > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2032 > URL: https://issues.jboss.org/browse/TEIIDDES-2032 > Project: Teiid Designer > Issue Type: Feature Request > Components: Usability > Affects Versions: 8.3.1 > Environment: JBTIS 4.1.3.Final > Reporter: Lucie Fabrikova > Priority: Minor > > In the "Create Web Service WAR File" dialog (vdb -> right click -> generate ws-cxf war), it is possible to set anything in field VDB JNDI Name. It is also possible to set invalid JNDI name: "java:teiidvdb" (bug in E2eYahoo testscript suggested this). > Maybe it would be good if the value in the field was validated... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1720) Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1720?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1720. ---------------------------------- Resolution: Won't Do > Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function > ------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1720 > URL: https://issues.jboss.org/browse/TEIIDDES-1720 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Modeling > Affects Versions: 7.8 > Reporter: Van Halbert > > When importing a text file, a model is created that has 1 procedure call in it, the getTextFiles() procedure. Would it be possible to get rid of this model and have the view model that references this, to call a System procedure? > I'm not sure if this has already been done in Designer 8.x. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1250) Need to improve the concept of how we're using and presenting the standard File and Web Service procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1250?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1250. ---------------------------------- Resolution: Won't Do > Need to improve the concept of how we're using and presenting the standard File and Web Service procedures > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1250 > URL: https://issues.jboss.org/browse/TEIIDDES-1250 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: Future > > Attachments: TEIIDDES-1250.txt > > > As we're developing more and more importers and model generators that utilize or require a source model containing getText(), getTextFiles(), invoke() or invokeHTTP(), it seems that we're spending a lot of time: > 1) Re-coding the logic to generate them to utilize the "Source" or connection profile stored in them > 2) Explaining to the user that this is "Required" and how/why it's happening. > The ONLY reason user-intervention is required is because currently, a Source model is needed as the carrier of the specific FILE or WSDL URL information. (Used to create "Data Source") > If this File/WSDL URL info was NOT included in these source models, then we could create a Built-in FileFunctions.xmi Source model that's delivered with the product and included in a VDB ANY time it's required. > To make this happen, we'd need another mechanism to persist the connection information and that might be the "View Model" that contains the SQL that contains the actual "File" or "URL" definition. This sort of makes sense. > I know our current "Preview Data" and "Create Data Source" framework only works with Source models, but if we could change this behavior we would save a LOT of pain and anguish for the user AND us developers in the future. > Currently this would simplify 3 different import wizards, remove a couple of Options in the "New > Teiid Metadata Model > Relational" wizard use case and remove a step or two from EACH cheat sheet or section in the documentation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-967) Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-967. --------------------------------- Resolution: Won't Do > Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-967 > URL: https://issues.jboss.org/browse/TEIIDDES-967 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Van Halbert > Fix For: Komodo > > > When keys/indexes are listed, they get in the way of viewing. They should be placed into their own folder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-441) Ability to get a list of dependencies for an object/element

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-441?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-441. --------------------------------- Resolution: Won't Do > Ability to get a list of dependencies for an object/element > ------------------------------------------------------------ > > Key: TEIIDDES-441 > URL: https://issues.jboss.org/browse/TEIIDDES-441 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Priority: Minor > Fix For: Future > > > We have found many instances in where we need to find out what other groups or transformations reference a particular group or element within a group. Basically, a two-way dependency report. In one way, we can see what elements/objects the selected element is dependent on. In the other way, we can see what objects or elements are dependent on the selected element. This will be very useful for refactoring and impact analysis within the Designer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-598) After inserting columns in table editor package diagram has weird scrolling region

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-598?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-598. --------------------------------- Resolution: Out of Date > After inserting columns in table editor package diagram has weird scrolling region > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-598 > URL: https://issues.jboss.org/browse/TEIIDDES-598 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: 7.1 > Reporter: Paul Nittel > Priority: Minor > Fix For: Future > > Attachments: OutOfOrderPackageDiagram.png > > > While writing up my previous bug, I noticed the package diagram had very strange spacing and a scrolling region where none was needed. See the attached screenshot. > I was able to reproduce this after restarting the Designer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-357) Would like XML Schema as Relational Source Model importer to accept sample XMLs or DTDs as well as XSDs

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-357?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-357. --------------------------------- Resolution: Won't Do > Would like XML Schema as Relational Source Model importer to accept sample XMLs or DTDs as well as XSDs > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-357 > URL: https://issues.jboss.org/browse/TEIIDDES-357 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > > The was a complaint that we were unable to build models for use with the XML-Relational connectors directly off their DTD (attached). Instead they had to use an external product to convert the DTD to an XSD, and then use the XSD as input to the importer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-381) New Operations and Inputs must be renamed in the Web Service model.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-381?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-381. --------------------------------- Resolution: Won't Do > New Operations and Inputs must be renamed in the Web Service model. > ------------------------------------------------------------------- > > Key: TEIIDDES-381 > URL: https://issues.jboss.org/browse/TEIIDDES-381 > Project: Teiid Designer > Issue Type: Bug > Environment: 553 RC1 > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > When you create a new Operation, or a new Input in a Web Service model, they are provided a default name. In order to provide a new name, you have to use the rename menu item. In contrast, when you create a new Table or Column in a Relational model, the new item is given focus in the model explorer and an edti box is opened to allow you the provide a name right away. We should be consistent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 closed TEIIDDES-344. --------------------------------- Resolution: Done This is now supported via TEIIDDES-2383 > 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 was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3165) Missing native and index metadata tag in .vdb when infinispan translator is overriding .vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3165?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3165. ------------------------------------ Resolution: Done merged > Missing native and index metadata tag in .vdb when infinispan translator is overriding .vdb > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3165 > URL: https://issues.jboss.org/browse/TEIIDDES-3165 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Matej Kralik > Priority: Critical > Fix For: 11.1.1 > > > According to this issue [TEIIDDES-3120|https://issues.jboss.org/browse/TEIIDDES-3120] The designer adds NATIVE an INDEX metadata tags to the .vdb when a model contains infinispan-hotrod translator. However, when the translator is overriding, the metadata are not added and designer by default override infinispan translator. Probably same solution as here [TEIIDDES-3142|https://issues.jboss.org/browse/TEIIDDES-3142] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2017