December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3168) OData4 Imported MXD properties have a space

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-3168: -------------------------------------- Summary: OData4 Imported MXD properties have a space Key: TEIIDDES-3168 URL: https://issues.jboss.org/browse/TEIIDDES-3168 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 11.1 Reporter: Ramesh Reddy Priority: Critical The Metadata Extension Properties that are imported from server for OData4 translator have leading space in the definition, thus it creates a wrong VDB which fails to run during the runtime {code} <p:property advanced="false" index="true" masked="false" name="Type" required="true" type="string"> <p:allowedValue>COMPLEX</p:allowedValue> <p:allowedValue> NAVIGATION</p:allowedValue> <p:allowedValue> COMPLEX_COLLECTION</p:allowedValue> <p:allowedValue> ENTITY_COLLECTION</p:allowedValue> <p:allowedValue> NAVIGATION_COLLECTION</p:allowedValue> <p:allowedValue> ENTITY</p:allowedValue> <p:allowedValue> FUNCTION</p:allowedValue> <p:allowedValue> ACTION</p:allowedValue> </p:property> {code} see allowed Values with leading white space. I am not sure this is how the server is providing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3097. ------------------------------------ Assignee: Barry LaFond Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/321d04765b98af7a0... Note that I retested the XML importer and the validation works fine. The commit from Nov 30th, may have happened after the last milestone build, so guessing you weren't quite testing that fix. > 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.1, 11.1 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png > > > 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)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3167) Teiid Connection Import - The deployment timeout once edited will not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3167?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3167: ----------------------------------- Priority: Critical (was: Major) > Teiid Connection Import - The deployment timeout once edited will not work > -------------------------------------------------------------------------- > > Key: TEIIDDES-3167 > URL: https://issues.jboss.org/browse/TEIIDDES-3167 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.1 > > > Using Teiid Designer 11.1 version (did not test older versions), during the import process using the Teiid Connection importer, if you change the default timeout property from 120 to any value (on the advanced tab) from there on any teiid connection importer deployments will fail with timeout. Even setting back to 120 will not work. > I feel the code somewhere may be interpreting the value as milliseconds instead of seconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3167) Teiid Connection Import - The deployment timeout once edited will not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3167?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3167: -------------------------------------- Assignee: Barry LaFond > Teiid Connection Import - The deployment timeout once edited will not work > -------------------------------------------------------------------------- > > Key: TEIIDDES-3167 > URL: https://issues.jboss.org/browse/TEIIDDES-3167 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 11.1.1 > > > Using Teiid Designer 11.1 version (did not test older versions), during the import process using the Teiid Connection importer, if you change the default timeout property from 120 to any value (on the advanced tab) from there on any teiid connection importer deployments will fail with timeout. Even setting back to 120 will not work. > I feel the code somewhere may be interpreting the value as milliseconds instead of seconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3167) Teiid Connection Import - The deployment timeout once edited will not work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3167?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3167: ----------------------------------- Fix Version/s: 11.1.1 > Teiid Connection Import - The deployment timeout once edited will not work > -------------------------------------------------------------------------- > > Key: TEIIDDES-3167 > URL: https://issues.jboss.org/browse/TEIIDDES-3167 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Fix For: 11.1.1 > > > Using Teiid Designer 11.1 version (did not test older versions), during the import process using the Teiid Connection importer, if you change the default timeout property from 120 to any value (on the advanced tab) from there on any teiid connection importer deployments will fail with timeout. Even setting back to 120 will not work. > I feel the code somewhere may be interpreting the value as milliseconds instead of seconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2865. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/106c74a98ec739c9a... > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2865 > URL: https://issues.jboss.org/browse/TEIIDDES-2865 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.1, 11.1 > > Attachments: debTest2Import.png, debtestImport.png, importedColumns.png > > > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly. > You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds > user - mss_eds > password - mss_eds > table - debtest2, both columns are numeric(9,2) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3034?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3034: ----------------------------------- Fix Version/s: 11.1.1 > 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, 11.1.1 > > 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)

8 years, 3 months

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: XMLafter.png XML.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 > Fix For: 11.1, 11.1.1 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png > > > 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)

8 years, 3 months

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: salesforce.png LDAPafter.png LDAP.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 > Fix For: 11.1, 11.1.1 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png > > > 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)

8 years, 3 months

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: ------------------------------------ I went through all imports wizards and I noticed some issues: # XML local or remote - teiid designer automatically add the name of the model without prefix in the JNDI name and I am able to continue (XML.png) but when I start writing to the label, the error appears (XMLafter.png). # LDAP - I am able to continue in wizard without any JNDI name (LDAP.png) but when I start writing to this label, I see the error (LDAPafter.png). # Salesforce - missing any checker (salesforce.png) # JDG 6.x connection profile - I am still able to add JNDI name without prefix > 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 > Fix For: 11.1, 11.1.1 > > Attachments: LDAP.png, LDAPafter.png, XML.png, XMLafter.png, jdgConnectionProfile.png, salesforce.png, webServiceJNDI.png > > > 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)

8 years, 3 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