May 2014 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2149) Simplify VDB Editor Layout

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2149?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2149: -------------------------------------- Assignee: Barry LaFond > Simplify VDB Editor Layout > -------------------------- > > Key: TEIIDDES-2149 > URL: https://issues.jboss.org/browse/TEIIDDES-2149 > Project: Teiid Designer > Issue Type: Enhancement > Components: Editors, VDB & Execution > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5 > > Attachments: new-vdb-editor-layout.png > > > VDB Editor is currently complex and contains 2 sets of always-visible tabs. The lower, except for the Description, could be termed "advanced" options. > 2 Options > * Create a second Editor tab labeled "Advanced" and label the main tab "Contents" > ** Could even give a "tree view" of the contents as well as Models, Other Files, and UDF Jars..? > or > * Change the bottom tab to a collapsible area which is activated with an "Advanced Settings...." link, similar to a number of dialogs. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2094: ----------------------------------- Fix Version/s: 8.5 > Support for dynamic extension metadata > --------------------------------------- > > Key: TEIIDDES-2094 > URL: https://issues.jboss.org/browse/TEIIDDES-2094 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.5 > > > Currently when Teiid core implements a new translator or customer/user implements a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it. > With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator. > Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server. > I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties. > Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2153) Create relational model from SOAP WS with Service Mode MESSAGE can't be finished

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2153?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2153: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/342 > Create relational model from SOAP WS with Service Mode MESSAGE can't be finished > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2153 > URL: https://issues.jboss.org/browse/TEIIDDES-2153 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Ted Jones > Priority: Blocker > Attachments: bug.png > > > Description of problem: > When I select Service Mode MESSAGE during the proccess of creating the relational model from SOAP WS it gets stuck and can't be finished. > How reproducible: > 1. Guides -> Generate relational model from WSDL > 2. Select some Connection Profile and some Operations > 3. Select Service Mode: MESSAGE, click Next> > 4. Leave default settings and click Next> again > 5. Nothing changes on the window only new error message in the top section of the window is displayed "No columns are defined for the response procedure result set for the operation: ... " and both buttons "Next>" and "Finish" are disabled > [see attachment] > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2153) Create relational model from SOAP WS with Service Mode MESSAGE can't be finished

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2153?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2153: -------------------------------- Fix Version/s: 8.5 8.3.3 > Create relational model from SOAP WS with Service Mode MESSAGE can't be finished > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2153 > URL: https://issues.jboss.org/browse/TEIIDDES-2153 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.2 > Reporter: Matus Makovy > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.5, 8.3.3 > > Attachments: bug.png > > > Description of problem: > When I select Service Mode MESSAGE during the proccess of creating the relational model from SOAP WS it gets stuck and can't be finished. > How reproducible: > 1. Guides -> Generate relational model from WSDL > 2. Select some Connection Profile and some Operations > 3. Select Service Mode: MESSAGE, click Next> > 4. Leave default settings and click Next> again > 5. Nothing changes on the window only new error message in the top section of the window is displayed "No columns are defined for the response procedure result set for the operation: ... " and both buttons "Next>" and "Finish" are disabled > [see attachment] > JBDS 7.1.1.GA + TeiidDesigner 8.3.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2154) Preview VDB is not updated after adding or modifying a translator override

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2154?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2154: ---------------------------------------- Fix for 8.3.3 will only include the patch for VdbModelEntry.getTranslatorOverride() method: {code} /** * Returns the current <code>TranslatorOverride</code> for this model * @return translator override. May be null. */ public final TranslatorOverride getTranslatorOverride() { if( !this.sourceInfo.isEmpty() ) { Set<TranslatorOverride> overrides = getVdb().getTranslators(); for( TranslatorOverride to : overrides) { for( VdbSource source : this.sourceInfo.getSources() ) { String translatorName = source.getTranslatorName(); if( translatorName != null && translatorName.toString().equalsIgnoreCase(to.getType()) ) { return to; } } } } return null; } {code} > Preview VDB is not updated after adding or modifying a translator override > -------------------------------------------------------------------------- > > Key: TEIIDDES-2154 > URL: https://issues.jboss.org/browse/TEIIDDES-2154 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.2 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5, 8.3.3 > > > If a preview VDB is created and then a translator override property is added or modified, the preview VDB is not updated. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2154) Preview VDB is not updated after adding or modifying a translator override

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2154?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2154: ----------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/commit/490f17a1d62955044... > Preview VDB is not updated after adding or modifying a translator override > -------------------------------------------------------------------------- > > Key: TEIIDDES-2154 > URL: https://issues.jboss.org/browse/TEIIDDES-2154 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.2 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.5, 8.3.3 > > > If a preview VDB is created and then a translator override property is added or modified, the preview VDB is not updated. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2154) Preview VDB is not updated after adding or modifying a translator override

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2154: ----------------------------------- Summary: Preview VDB is not updated after adding or modifying a translator override Key: TEIIDDES-2154 URL: https://issues.jboss.org/browse/TEIIDDES-2154 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 8.3.2 Reporter: Ted Jones Assignee: Barry LaFond Priority: Critical Fix For: 8.5, 8.3.3 If a preview VDB is created and then a translator override property is added or modified, the preview VDB is not updated. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2135) Parse Error Persists After Correcting Query

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2135?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-2135. --------------------------------------- Resolution: Done > Parse Error Persists After Correcting Query > ------------------------------------------- > > Key: TEIIDDES-2135 > URL: https://issues.jboss.org/browse/TEIIDDES-2135 > Project: Teiid Designer > Issue Type: Feature Request > Components: Validation > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Paul Richardson > Fix For: 8.5 > > > After incurring a parse error in the sql transformation error, the parse error remains even after correcting the sql. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2100) Add ability to migrate older models containing table names with "." characters

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2100?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2100: ----------------------------------- Attachment: BarryProducts.zip > Add ability to migrate older models containing table names with "." characters > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2100 > URL: https://issues.jboss.org/browse/TEIIDDES-2100 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations, Validation > Affects Versions: 8.4, 8.3.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.5, 8.3.3 > > Attachments: BarryProducts.zip > > > DV 6 tooling (Designer 8.3.x) includes error validation to prevent non-quoted names from being defined and used in SQL. > Designer needs a mechanism/framework to help users globally fix table names containing the "." delimiter. > Options: > # Designer feature/action to "fix" a model > # simple CLI-based app to apply to a model > Need to investigate our "rename" logic to see if it can handle the cascade effect of changing table name and fixing dependent SQL -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2100) Add ability to migrate older models containing table names with "." characters

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2100?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2100: ---------------------------------------- Examples we need to handle TABLE NAME: *products.productdata* * Simple Select SQL >>> SELECT * FROM ProductsSource.products.productdata * fix would be to wrap the in d-quotes >>> *"products.productData"* TABLE NAME: *"products.productData"* * SQL ends up as >>> SELECT * FROM ProductsSource."""products"."productdata""" * SQL should end up >>> SELECT * FROM ProductsSource."products.productdata" > Add ability to migrate older models containing table names with "." characters > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2100 > URL: https://issues.jboss.org/browse/TEIIDDES-2100 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations, Validation > Affects Versions: 8.4, 8.3.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.5, 8.3.3 > > > DV 6 tooling (Designer 8.3.x) includes error validation to prevent non-quoted names from being defined and used in SQL. > Designer needs a mechanism/framework to help users globally fix table names containing the "." delimiter. > Options: > # Designer feature/action to "fix" a model > # simple CLI-based app to apply to a model > Need to investigate our "rename" logic to see if it can handle the cascade effect of changing table name and fixing dependent SQL -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2014