September 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2554) Import of REST service with columns set to 'integer' type results in "Expected biginteger, but was integer."

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2554?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-2554. --------------------------------- Resolution: Done This was also an issue with the SOAP importer. We have deprecated the design-time "integer" data type in Designer. I have made the following changes: For SOAP, if an element type is "integer", it will be converted to "biginteger". The "integer" type will not display in the datatype dropdown of the column editor. For REST, the "integer" type will not display in the datatype dropdown of the column editor. > Import of REST service with columns set to 'integer' type results in "Expected biginteger, but was integer." > ------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2554 > URL: https://issues.jboss.org/browse/TEIIDDES-2554 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Web Services Support > Affects Versions: 9.0.1 > Reporter: Marc Shirley > Assignee: Ted Jones > Fix For: 9.0.4, 9.2 > > > Importing posts service from http://jsonplaceholder.typicode.com results in "Expected biginteger, but was integer." runtime error when previewing procedure. This appears to be an issue with the type assignments on the model as a dynamic VDB using the same invocation executes properly. Also seems similar to the issue described in TEIIDDES-2438. > Full error is: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30492 TEIID31121 The expected result set of the procedure ViewModel.postById does not match the result set from returnable statement SELECT A.id AS id, A.userId AS userId, A.title AS title, A.body AS body FROM (EXEC SourceModel.invokeHttp(action => 'GET', endpoint => VARIABLES.qp, stream => 'TRUE')) AS f, XMLTABLE('/response' PASSING JSONTOXML('response', f.result) COLUMNS id integer PATH 'id/text()', userId integer PATH 'userId/text()', title string PATH 'title/text()', body string PATH 'body/text()') AS A; use WITHOUT RETURN to indicate the statement should not be returned - The definition for ViewModel.postById has the wrong type for column 1. Expected biginteger, but was integer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2635) Provide manageability of DDL based models/vdb's and .xmi models

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2635?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-2635: ------------------------------------- Assignee: Barry LaFond > Provide manageability of DDL based models/vdb's and .xmi models > ---------------------------------------------------------------- > > Key: TEIIDDES-2635 > URL: https://issues.jboss.org/browse/TEIIDDES-2635 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Reporter: Van Halbert > Assignee: Barry LaFond > > Copying comments from planning: > Per Ramesh, the suggestion/proposal (we talked about this couple times) is to keep a DDL version of the Model along with the XMI model in separate tab in the Designer and let users check in the DDL version into the SVN/GIT using "team" feature in the Eclipse. Since DDL file will be text based, the merge and diff are facilities provided through Eclipse tools. We need to use the team import feature to update the XMI model when reading from SVN/GIT. This will give us closest collaboration platform we are looking for without waiting for Komodo and I believe it is fairly achievable goal. > Barry: > The initial import/export (generate) features for dynamic vdbs perform the needed operations. Now that we have both *.vdb and -vdb.xml resources we can think more about how to assist the user. CSV/GIT in Eclipse is certainly an attractive option. Linking a -vdb.xml file to a *.vdb and auto-saving both is also an option. And as Van said, differencing via CSV/GIT would be the direction I'd vote for. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2635) Provide manageability of DDL based models/vdb's and .xmi models

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2635: ------------------------------------- Summary: Provide manageability of DDL based models/vdb's and .xmi models Key: TEIIDDES-2635 URL: https://issues.jboss.org/browse/TEIIDDES-2635 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Usability Reporter: Van Halbert Copying comments from planning: Per Ramesh, the suggestion/proposal (we talked about this couple times) is to keep a DDL version of the Model along with the XMI model in separate tab in the Designer and let users check in the DDL version into the SVN/GIT using "team" feature in the Eclipse. Since DDL file will be text based, the merge and diff are facilities provided through Eclipse tools. We need to use the team import feature to update the XMI model when reading from SVN/GIT. This will give us closest collaboration platform we are looking for without waiting for Komodo and I believe it is fairly achievable goal. Barry: The initial import/export (generate) features for dynamic vdbs perform the needed operations. Now that we have both *.vdb and -vdb.xml resources we can think more about how to assist the user. CSV/GIT in Eclipse is certainly an attractive option. Linking a -vdb.xml file to a *.vdb and auto-saving both is also an option. And as Van said, differencing via CSV/GIT would be the direction I'd vote for. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2495) Allow "No Timeout" Value for the Teiid Connection Importer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2495?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2495. ------------------------------------- Resolution: Done The timeout preference value is now exposed in the wizard. The user does not need to exit the wizard to change it. A timeout value of zero is now used for 'no timeout'... https://github.com/Teiid-Designer/teiid-designer/pull/490 > Allow "No Timeout" Value for the Teiid Connection Importer > ---------------------------------------------------------- > > Key: TEIIDDES-2495 > URL: https://issues.jboss.org/browse/TEIIDDES-2495 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 9.0.4, 9.2 > > > Allow a "No Timeout" value in the Teiid Connection importer (something like 0 or -1) that will allow the import to continue until finished or canceled. The current override value only goes to 999 which may not be long enough for some sources. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2494) Cancel on Teiid Connection Import Not Working

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2494?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2494. ------------------------------------- Resolution: Done The user can now cancel the import. https://github.com/Teiid-Designer/teiid-designer/pull/490 > Cancel on Teiid Connection Import Not Working > --------------------------------------------- > > Key: TEIIDDES-2494 > URL: https://issues.jboss.org/browse/TEIIDDES-2494 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Mark Drilling > Fix For: 9.0.4, 9.2 > > > Clicking cancel when importing a Teiid connection is has no affect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2435: ------------------------------------------- [~van.halbert] Can you be more specific as to 'blanked out'? Do you mean the box does not display the username so instead shows '****' or do you mean there should be no username populated at all by default? Thanks PGR > [Usability] The default user when connecting to server should be blanked out > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2435 > URL: https://issues.jboss.org/browse/TEIIDDES-2435 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 9.2 > > > In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2550) parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2550?page=com.atlassian.jira.plu... ] Paul Richardson updated TEIIDDES-2550: -------------------------------------- Attachment: ParseTimestamp-Project.png Hey [~daan-isaac] I am more than a little curious. I have installed 9.1.Final, opened the project and displayed the transformation editor. Only everything seems fine. I have attached a screenshot to demonstrate. Maybe, we are looking at different parts of the application? Any thoughts? Paul > parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2550 > URL: https://issues.jboss.org/browse/TEIIDDES-2550 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Transformations > Affects Versions: 9.1 > Environment: Teiid 8.7.1.redhat-8 and Teiid Designer 9.1.0.Beta1 > Reporter: Daan Creemers > Assignee: Paul Richardson > Fix For: 9.2 > > Attachments: ParseTimestamp-Project.png, TestParseTimestamp.tar.gz > > > When using the parseTimestamp function in the transformation editor while creating a relational view model, a StringIndexOutOfBoundsException is thrown. The query SELECT parseTimestamp('18:10:20', 'HH:mm:ss') is used in the transformation editor which gives 'String index out of range: 1'. I want to use the function with a column of my table but produces the same error. > When deploying a virtual database and executing exactly the same query on the database, the query finishes successfully and gives the result. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2478) LDAP import functionality does not handle large number of search results

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2478?page=com.atlassian.jira.plu... ] Paul Richardson edited comment on TEIIDDES-2478 at 9/3/15 9:20 AM: ------------------------------------------------------------------- Merged into master. Awating decision on 9.0.x branch was (Author: phantomjinx): Merged into master > LDAP import functionality does not handle large number of search results > ------------------------------------------------------------------------ > > Key: TEIIDDES-2478 > URL: https://issues.jboss.org/browse/TEIIDDES-2478 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Marc Shirley > Assignee: Paul Richardson > Fix For: 9.0.4, 9.2 > > > LDAP import mechanism does not include paging for when large result sets are returned by the LDAP server. This can result in the importer not including necessary objects and displaying an error like "LDAP: error code 4 - Sizelimit Exceeded". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2480) LDAP importer fails silently when no location is explicitly entered for the new model

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2480?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2480: ------------------------------------------- Merged into master. Awating decision on 9.0.x branch > LDAP importer fails silently when no location is explicitly entered for the new model > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-2480 > URL: https://issues.jboss.org/browse/TEIIDDES-2480 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Marc Shirley > Assignee: Paul Richardson > Fix For: 9.0.4, 9.2 > > > LDAP import fails silently when no location is entered for the "Source Model Definition" section's "Location" field on the first page of the wizard. This occurs even when using the context menu to initiate from a specific project or child object level. The wizard functions as expected until you finish, at which point the model is never generated. No error dialog or failure notification is presented to the user. checking error log shows: > java.lang.NullPointerException > at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.createNewModelResource(RelationalModelBuilder.java:65) > at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.modelEntries(RelationalModelBuilder.java:109) > at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizardManager.createModel(LdapImportWizardManager.java:384) > at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizard$1.run(LdapImportWizard.java:158) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2478) LDAP import functionality does not handle large number of search results

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2478?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-2478: ------------------------------------------- Merged into master > LDAP import functionality does not handle large number of search results > ------------------------------------------------------------------------ > > Key: TEIIDDES-2478 > URL: https://issues.jboss.org/browse/TEIIDDES-2478 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Marc Shirley > Assignee: Paul Richardson > Fix For: 9.0.4, 9.2 > > > LDAP import mechanism does not include paging for when large result sets are returned by the LDAP server. This can result in the importer not including necessary objects and displaying an error like "LDAP: error code 4 - Sizelimit Exceeded". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2015