January 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2720) Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2720?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2720: ----------------------------------- Attachment: export-dynamic-vdb-status-dialog.png > Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB > -------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2720 > URL: https://issues.jboss.org/browse/TEIIDDES-2720 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export, Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2.1 > > Attachments: export-dynamic-vdb-status-dialog.png > > > [~blafond]: > {quote}WS Operations are really just Virtual Procedures, so we could convert WS models in the near term{quote} > Exporting VDB with a web service model currently results in an empty model. Add the ability to export WS operations as virtual procedures. > Provide checks on VDB export and warn users if XML Document, Web Services or XSD models exist in the VDB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2437) Enable specifying VDB Version when using VDB RE-USE feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2437?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2437: ----------------------------------- Attachment: import-vdb-dialog.png > Enable specifying VDB Version when using VDB RE-USE feature > ----------------------------------------------------------- > > Key: TEIIDDES-2437 > URL: https://issues.jboss.org/browse/TEIIDDES-2437 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, VDB & Execution > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.2.1 > > Attachments: import-vdb-dialog.png > > > When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. > <import-vdb name="Products" version="3" import-data-policies="true"/> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2437) Enable specifying VDB Version when using VDB RE-USE feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2437?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2437. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/2f7ba9b3e5ab41baa... > Enable specifying VDB Version when using VDB RE-USE feature > ----------------------------------------------------------- > > Key: TEIIDDES-2437 > URL: https://issues.jboss.org/browse/TEIIDDES-2437 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, VDB & Execution > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.2.1 > > Attachments: import-vdb-dialog.png > > > When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. > <import-vdb name="Products" version="3" import-data-policies="true"/> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2763) User cannot delete last parameter on REST connection profile while editing

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2763: -------------------------------------- Summary: User cannot delete last parameter on REST connection profile while editing Key: TEIIDDES-2763 URL: https://issues.jboss.org/browse/TEIIDDES-2763 Project: Teiid Designer Issue Type: Bug Environment: MAC Reporter: Matus Makovy Attachments: bug.mov I delete the last parameter on REST connection profile, hit Apply and OK. Then I click Edit to check if it is deleted and the parameter is still there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2725: ----------------------------------- Attachment: Screen Shot 2016-01-19 at 14.45.34.png > Transformation sql is not correct when using REST import with URL attributes > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2725 > URL: https://issues.jboss.org/browse/TEIIDDES-2725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Assignee: Ted Jones > Fix For: 9.2.1 > > Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png, Screen Shot 2016-01-19 at 14.45.34.png > > > When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. > ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* > SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2725) Transformation sql is not correct when using REST import with URL attributes

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2725: ------------------------------------ I am still able to reproduce this with TD 9.0.5 and Java 7 on Mac. I cannot test it with Java 8 because of TEIIDDES-2762. Screenshot attached > Transformation sql is not correct when using REST import with URL attributes > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2725 > URL: https://issues.jboss.org/browse/TEIIDDES-2725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Assignee: Ted Jones > Fix For: 9.2.1 > > Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at 15.22.59.png, Screen Shot 2016-01-19 at 14.45.34.png > > > When you use connection parameters in REST connection profile definition, the resulting transformation SQL generated during import from this CP is malformed. > ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+* ViewModel.getCases.newSearch AS newSearch *+|| '/' || ViewModel.getCases.newSearch+* > SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug Description, not in screenshot) > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2760: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2760. ---------------------------------- > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2704) Changing models results in unmodified models being marked changed by Eclipse

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2704?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2704: ----------------------------------- Labels: release_notes verified_jbdsis-8.0.5 (was: ) > Changing models results in unmodified models being marked changed by Eclipse > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2704 > URL: https://issues.jboss.org/browse/TEIIDDES-2704 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Patch Release > Affects Versions: 9.0.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > Making changes in one model can result in other models being marked as changed even though they are unmodified by the user. In the reproduction steps, making a change to a transformation in one model results in changes to a related model that is unmodified by the user. When closing and discarding changes in the related model, additional changes (not initiated by the user) are made to the original model. These Eclipse-initiated changes seem to result in reference errors when building the model if they are saved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2704) Changing models results in unmodified models being marked changed by Eclipse

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2704?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2704. ---------------------------------- > Changing models results in unmodified models being marked changed by Eclipse > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2704 > URL: https://issues.jboss.org/browse/TEIIDDES-2704 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Patch Release > Affects Versions: 9.0.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-8.0.5 > Fix For: 9.0.5, 9.2.1 > > > Making changes in one model can result in other models being marked as changed even though they are unmodified by the user. In the reproduction steps, making a change to a transformation in one model results in changes to a related model that is unmodified by the user. When closing and discarding changes in the related model, additional changes (not initiated by the user) are made to the original model. These Eclipse-initiated changes seem to result in reference errors when building the model if they are saved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2016