December 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2945) Issues with ddl generation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2945?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2945. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/de9ec9343d7ce82ff... > Issues with ddl generation > -------------------------- > > Key: TEIIDDES-2945 > URL: https://issues.jboss.org/browse/TEIIDDES-2945 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.1 > Reporter: Steven Hawkins > Fix For: 11.1 > > > This can be separated out into separate issues if needed. > - most ddl statements are not terminated with the semicolon delimiter. This was a mistake with the original grammar. We'll hopefully get this resolved with minimal breaking changes with TEIID-4528 > - name in source and other options should be added by default. Is there a reason they are omitted by default? > - triggers / update procedures don't seem to be emitted -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2945) Issues with ddl generation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2945?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2945: ------------------------------------------ Using TD 11.0, the third item or trigger/update procedures do appear in the DDL. The check boxes for name in source and native type still default to unchecked - they should be checked by default. And semicolons are not being added after all statements, such as create trigger/view. A minor thing, http://teiiddesigner.jboss.org/designer_summary/downloads.html in the 11.0 instructions references Designer version 10.1. > Issues with ddl generation > -------------------------- > > Key: TEIIDDES-2945 > URL: https://issues.jboss.org/browse/TEIIDDES-2945 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.1 > Reporter: Steven Hawkins > Fix For: 11.1 > > > This can be separated out into separate issues if needed. > - most ddl statements are not terminated with the semicolon delimiter. This was a mistake with the original grammar. We'll hopefully get this resolved with minimal breaking changes with TEIID-4528 > - name in source and other options should be added by default. Is there a reason they are omitted by default? > - triggers / update procedures don't seem to be emitted -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2945) Issues with ddl generation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2945?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2945: ------------------------------------------ Yes, I'll have a look > Issues with ddl generation > -------------------------- > > Key: TEIIDDES-2945 > URL: https://issues.jboss.org/browse/TEIIDDES-2945 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.1 > Reporter: Steven Hawkins > Fix For: 11.1 > > > This can be separated out into separate issues if needed. > - most ddl statements are not terminated with the semicolon delimiter. This was a mistake with the original grammar. We'll hopefully get this resolved with minimal breaking changes with TEIID-4528 > - name in source and other options should be added by default. Is there a reason they are omitted by default? > - triggers / update procedures don't seem to be emitted -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2682) Importing Teiid DDL and selecting wrong model type results in error

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2682?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2682. ------------------------------------ Resolution: Out of Date fix was to provide a separate Teiid DDL import option > Importing Teiid DDL and selecting wrong model type results in error > ------------------------------------------------------------------- > > Key: TEIIDDES-2682 > URL: https://issues.jboss.org/browse/TEIIDDES-2682 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.4 > Environment: MAC OS > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 11.1 > > Attachments: Screen Shot 2015-10-12 at 13.32.49.png, view.ddl > > > When you import Teiid DDL that was created as export from VIEW MODEL and you select SOURCE MODEL during the import, this process results in error dialogue that is not really helpful for user. (see screenshot) > I think the error message should be more accurate -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2945) Issues with ddl generation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2945?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2945: ---------------------------------------- [~shawkins] Can you try generating dyn. VDB with triggers/updates in a view.... again with Designer 10.0.2 or 11.0? I add this back in August and tested again. Seems to work? Thx > Issues with ddl generation > -------------------------- > > Key: TEIIDDES-2945 > URL: https://issues.jboss.org/browse/TEIIDDES-2945 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.1 > Reporter: Steven Hawkins > Fix For: 11.1 > > > This can be separated out into separate issues if needed. > - most ddl statements are not terminated with the semicolon delimiter. This was a mistake with the original grammar. We'll hopefully get this resolved with minimal breaking changes with TEIID-4528 > - name in source and other options should be added by default. Is there a reason they are omitted by default? > - triggers / update procedures don't seem to be emitted -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2978) In the materialize wizard, split out the cacheTypeMap

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2978?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2978: ----------------------------------- Fix Version/s: 11.2 (was: 11.1) > In the materialize wizard, split out the cacheTypeMap > ----------------------------------------------------- > > Key: TEIIDDES-2978 > URL: https://issues.jboss.org/browse/TEIIDDES-2978 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling, Usability > Affects Versions: 10.0.3 > Reporter: Van Halbert > Priority: Optional > Fix For: 11.2 > > > - change the cacheTypeMap to be split out into 3 separate text boxes for the user (cache name, class name, primary key) > a. the primary key from the view (if it exists) can be use to set the default for the primary key > b. the class name can be defaulted to what the pojo class to be created > c. The user then only needs to enter the cache name > All three must be entered to complete process > under the covers, the property will be assembled: cacheName + ":" + classname + ":" + primarykey -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2900) Delete Resource Refactoring framework needs work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2900?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2900: ----------------------------------- Fix Version/s: 11.2 (was: 11.1) > Delete Resource Refactoring framework needs work > ------------------------------------------------ > > Key: TEIIDDES-2900 > URL: https://issues.jboss.org/browse/TEIIDDES-2900 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Affects Versions: 10.0.1, 10.1 > Reporter: Barry LaFond > Fix For: 11.2 > > > Currently when you delete a View model, only the view model is deleted as long as it isn't used/referenced in another view model. > If a user selects a source model, any view models that depend on the source model will also be selected for deletion. > This seems overkill. > The old Delete model framework, deleted only the selected resource and it walked through any dependent models and cleaned up any references to the model being deleted. > So suggesting that we restore the single-resource delete (for models especially) and restore the model clean-up to insure that references are removed (i.e. transformation mappings) as well as the model import. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2529) 1024 x 768 Issue with XML model editor - can not reach red "Staging table arrow" when scrolling

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2529?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2529: ----------------------------------- Fix Version/s: Future (was: 11.1) > 1024 x 768 Issue with XML model editor - can not reach red "Staging table arrow" when scrolling > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2529 > URL: https://issues.jboss.org/browse/TEIIDDES-2529 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.2 > Reporter: Matus Makovy > Fix For: Future > > Attachments: Screen Shot 2015-05-18 at 4.30.23 PM.png, Screen Shot 2015-05-18 at 4.30.30 PM.png, Screen Shot 2015-05-18 at 4.30.32 PM.png, bug.mov > > > I am trying to add transformation source. I have to right-click "red arrow" in the model editor and I am not able to reach it. > Screenshots + video attached > Issue occured on OS X -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2564) Add support to support comments in VDB XML manifest

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2564?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2564: ----------------------------------- Fix Version/s: Future (was: 11.1) Not sure if this is needed in Designer. Also appears that general comments are only partially implemented in DynamicVdb.java class. Pushing to future > Add support to support comments in VDB XML manifest > --------------------------------------------------- > > Key: TEIIDDES-2564 > URL: https://issues.jboss.org/browse/TEIIDDES-2564 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Reporter: Barry LaFond > Fix For: Future > > > Dynamic VDBs are XML files that supports general comments. We need to make sure that Designer's VDB Manifest business object supports reading and writing these comments. > This will be critical for the new import/export dynamic VDB features. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2748: ----------------------------------- Fix Version/s: 11.2 (was: 11.1) > ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2748 > URL: https://issues.jboss.org/browse/TEIIDDES-2748 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Minor > Fix For: 11.2 > > > Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected. > On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked. > On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation> > The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 2016