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

[JBoss JIRA] (TEIIDDES-3034) Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3034?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3034. ---------------------------------- [~blafond] The model from the comment is still invalid in the JBDS but I noticed that it is not invalid itself, just I have to validate it in the transformation editor manually. So, I created the new bug for this behavior [TEIIDDES-3198|https://issues.jboss.org/browse/TEIIDDES-3198] and I have closed this JIRA. > Importing Virtual Procedure DDL containing a simple RETURNS type add a Result Set to procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3034 > URL: https://issues.jboss.org/browse/TEIIDDES-3034 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: viewModelFromComment.png, viewModelFromDescription.png > > > testing and debugging for TEIIDDES-2783 exposed an issue when importing a procedure containing a RETURNS data type and no result set. > The transformation resolving framework contains logic that will auto-create a result set containing a generated column. > We need to catch this use-case and prevent the result set from being created using this simple DDL input > {code} > CREATE VIRTUAL PROCEDURE ProcedureWithRS ( > stringIN string(4000) OPTIONS(ANNOTATION 'parameter 1 description') > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') AS > BEGIN > SELECT stringIN AS result; > END > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3198) JBDS marks imported model as invalid

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3198: -------------------------------------- Summary: JBDS marks imported model as invalid Key: TEIIDDES-3198 URL: https://issues.jboss.org/browse/TEIIDDES-3198 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 11.1.3 Reporter: Matej Kralik Attachments: comment.ddl, description.ddl, validateModel.mkv When I generate view model from the DDL (comment.ddl in the attachments), JBDS shows that model contains errors. However, when I click on the transformation editor, the model is updated, but still not valid. After that, I am not able to click on the Save/Valid SQL button so I have to add and remove the character to the transformation editor. When I click on the Save/Valid SQL button and save the model, the model looks validated and errors are gone. Why is the view model not valid after generated? I have uploaded video to the attachments. This has to be specific for that DDL (comment.ddl) because for another DDL(description.ddl), a view model is already valid after generated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3076) executed vdbs and query previews completely freeze designer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3076?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3076. ---------------------------------- I am not able to reproduce it in the latest Teiid Designer so I have closed this issues. [~mechevar] If you are still able to reproduce it, feel free to reopen this JIRA. When I set "generate plans preference" in the Teiid Execution Plan as ENABLED, the SELECT * takes a little bit longer as when I set as DISABLED. Maybe for the large result sets and cross modeling, Generate plans takes much longer. > executed vdbs and query previews completely freeze designer > ----------------------------------------------------------- > > Key: TEIIDDES-3076 > URL: https://issues.jboss.org/browse/TEIIDDES-3076 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 11.0.1 > Environment: JBoss Developer Studio 10.3.0, Linux > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.2 > > Attachments: Screenshot from 2017-05-02 16-12-41.png, jdv-api.zip > > > Previewing or querying within JBDS 10 against combinations of file based sources hangs the designer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3195) Preview VDB from salesforce source model has wrong namespace set

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3195?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-3195: ---------------------------------------- [~blafond] Yes, if this is the case then we need to change this to a blocker and fix it in every one of them. The alert that I got after deploying this VDB specifically said that it cannot contain curly brackets. > Preview VDB from salesforce source model has wrong namespace set > ---------------------------------------------------------------- > > Key: TEIIDDES-3195 > URL: https://issues.jboss.org/browse/TEIIDDES-3195 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.3 > Reporter: Matus Makovy > Priority: Critical > > The VDB that is created for preview of salesforce source model has namespace set to: > {code:xml} > <metadata type="DDL"><![CDATA[ > SET NAMESPACE '{http://www.teiid.org/translator/salesforce/2012}' AS teiid_sf > {code} > This is not correct, the correct statement is: > {code:xml} > <metadata type="DDL"><![CDATA[ > SET NAMESPACE 'http://www.teiid.org/translator/salesforce/2012' AS teiid_sf > {code} > without curly brackets -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3087: ----------------------------------- Attachment: connectionTypeNone.mkv > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: connectionTypeNone.mkv > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3087: ------------------------------------ Still, I am able to reproduce it. After creating VDB, the connection type is set to NONE (in the vdb editor) but vdb.xml doesn't contain connection type element and I have to change the (Connection type in the vdb editor) to another and back to NONE if I want to have NONE connection type in my VDB. I have uploaded the video. But, when the default state of the VDB is without any connection type[1], the vdb editor shouldn't by show NONE connection type by default because the user should misunderstand that the VDB contains this connection type element. [1] According to the [documentation|https://teiid.gitbooks.io/documents/content/admin/VDB_Versioning.html], by default, VDB should contain BY_VERSION connection type. It is the same as when VDB doesn't contain any connection type? If it is true, the vdb editor should set BY_VERSION as default connection type. > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.2 > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3097: ----------------------------------- Attachment: salesforce11.1.3.png > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, salesforce11.1.3.png, webServiceJNDI.png, xmlImporter.mkv > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik commented on TEIIDDES-3097: ---------------------------------------- In the salesforce importer, the checker works and shows error, but still, I am able to click on the Finish button. (salesforce11.1.3.png) > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, salesforce11.1.3.png, webServiceJNDI.png, xmlImporter.mkv > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3097: ----------------------------------- Attachment: xmlImporter.mkv > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png, xmlImporter.mkv > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3097: ------------------------------------ XML importer (local and remote) still doesn't check generated name. When I add some char to the name, checker works, but checker doesn't check whether first generated JNDI name contains prefix java:/ or not. I have uploaded video. > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.1.2 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png, xmlImporter.mkv > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2018