August 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2589) The model extension definition "relational" found in model is a different version than the one in the registry.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2589?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2589: ----------------------------------- Labels: (was: release_notes verified_jbdsis-9.0.0.Beta) > The model extension definition "relational" found in model is a different version than the one in the registry. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2589 > URL: https://issues.jboss.org/browse/TEIIDDES-2589 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0, 9.0.1, 9.1, 9.0.2 > Reporter: Lukas Mro > Assignee: Barry LaFond > Fix For: 10.0, 9.2.1 > > > After importing model from TD 8.1.0 to 9.X.X two types of errors occures > 3 types of errors occures: > 1. The model extension definition "rest" found in model is not registered in workspace -> this one can be autofix > 2. The model extension definition "relational" found in model is a different version than the one in the registry -> This one do not have fix > 3. java.lang.StringIndexOutOfBoundsException: String index out of range: 1 > -> this one do not have fix > I`m not sure what should i send you, AMA :) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2891) JBoss studio freezes after addition second default source in VDB editor

by Mario Majernik (JIRA)

Mario Majernik created TEIIDDES-2891: ---------------------------------------- Summary: JBoss studio freezes after addition second default source in VDB editor Key: TEIIDDES-2891 URL: https://issues.jboss.org/browse/TEIIDDES-2891 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 10.0.1 Reporter: Mario Majernik Attachments: ScreenShot_1.png, XmlSchemalessProject.zip After addition second source with default names ( Source Name : Name_1 ; Translator Name : TRANSLATOR_NAME ; JNDI Name : JNDI_NAME) to some model in VBD editor JBoss studio freezes. All unsaved changes are lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2388: ---------------------------------------- [~van.halbert] There is still this issue with JDG: TEIIDDES-2852. TD sets the translator according to driver name, if there will be no driver for JDG on the first page, I am not sure how the translator will be set correctly. > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release, Teiid Integration > Affects Versions: 8.6.1 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Blocker > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0, 9.2.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://<host>:3<instance number>15" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2388: --------------------------------------- This also happens when importing a JDG resource. > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release, Teiid Integration > Affects Versions: 8.6.1 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Blocker > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0, 9.2.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://<host>:3<instance number>15" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2890) After selecting SAP Hana datasource the translator is set to Jdbc ansi

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2890?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2890: ---------------------------------------- PRs: 10.0.x: https://github.com/Teiid-Designer/teiid-designer/pull/557 master: https://github.com/Teiid-Designer/teiid-designer/pull/558 > After selecting SAP Hana datasource the translator is set to Jdbc ansi > ---------------------------------------------------------------------- > > Key: TEIIDDES-2890 > URL: https://issues.jboss.org/browse/TEIIDDES-2890 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Matus Makovy > Priority: Minor > > When you choose SAP Hana datasource (DS that uses sap hana driver) the translator on next page is set to jdbc ansi. > Server has 'hana' translator. So I think this translator should be selected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2388: ---------------------------------------- This is included in TD 10.0.1, but [~skaleta] noticed that translator is set to JDBC ansi, see TEIIDDES-2890. > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release, Teiid Integration > Affects Versions: 8.6.1 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Blocker > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0, 9.2.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://<host>:3<instance number>15" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2890) After selecting SAP Hana datasource the translator is set to Jdbc ansi

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2890: -------------------------------------- Summary: After selecting SAP Hana datasource the translator is set to Jdbc ansi Key: TEIIDDES-2890 URL: https://issues.jboss.org/browse/TEIIDDES-2890 Project: Teiid Designer Issue Type: Bug Affects Versions: 10.0.1 Reporter: Matus Makovy Assignee: Matus Makovy Priority: Minor When you choose SAP Hana datasource (DS that uses sap hana driver) the translator on next page is set to jdbc ansi. Server has 'hana' translator. So I think this translator should be selected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2889) Inconsistent errors in Problems View

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2889?page=com.atlassian.jira.plu... ] Matej Kralik edited comment on TEIIDDES-2889 at 8/3/16 6:53 AM: ---------------------------------------------------------------- [~blafond] I think that this error is valid. (According to TEIIDDES-2414 ) After the designer generated models (from csv file), I clicked to Project>Clean and the error appeared in the Problems view. Anyway, I think that the error should appear immediately after the designer generated models because users have no idea that something is wrong. Users can create VDB and they still haven't seen any problem. After they deploy VDB (a server shows error (TEIID80004 Model ViewModel not found)) they becoming aware that they have errors in the project. I think that the Problems view needs some "trigger" for refresh (In my example it is rename project or click to Project>Clean) was (Author: mkralik): [~blafond] I think that this error is valid. (According to TEIIDDES-2414 ) After the designer generated models (from csv file), I clicked to Project>Clean and the error appeared in the Problems view. Anyway, I think that the error should appear immediately after the designer generated models because users have no idea that something is wrong. Users can create VDB and they still haven't seen any problem. After they deploy VDB (a server shows error (TEIID80004 Model ViewModel not found)) they becoming aware that they have errors in the project. I think that the Problems view needs some "trigger" for refresh (in my way it is rename project or click to Project>Clean) > Inconsistent errors in Problems View > ------------------------------------ > > Key: TEIIDDES-2889 > URL: https://issues.jboss.org/browse/TEIIDDES-2889 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations, Views > Affects Versions: 10.0.1 > Reporter: stanislav kaleta > Attachments: ProductsInfo.wsdl, screenshot1.png, screenshot2.png > > > Errors which occur in Designer (e.g. Transformation Editor) are not showed in Problems View immediately. Some of them appears after another action (e.g. rename project) or after VDB creation. On the other hand, some errors which were resolved in Designer remain present in Problems View. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2783: ----------------------------------- Attachment: screenshot1.png procedureProject.zip > Need to add support for parsing OPTIONS in procedure statements > --------------------------------------------------------------- > > Key: TEIIDDES-2783 > URL: https://issues.jboss.org/browse/TEIIDDES-2783 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Dan Florian > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0 > > Attachments: procedureProject.zip, screenshot1.png > > > The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause. > CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer > {code} > CREATE FOREIGN PROCEDURE ProcedureWithRS ( > newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'), > newParameter_2 string(4000) > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2783) Need to add support for parsing OPTIONS in procedure statements

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-2783: ------------------------------------ This is not fixed in TD 10.0.1.Final When I tied this DDL: {code:java} CREATE VIRTUAL PROCEDURE selfProc (stringIN string(4000) OPTIONS(ANNOTATION 'parameter description')) RETURNS OPTIONS(ANNOTATION 'resultset description') TABLE (result string(30)) OPTIONS(ANNOTATION 'procedure description') AS BEGIN SELECT viewModel.selfProc.stringIN AS result; END; {code} ResultSet description is not set correctly. In the result set description is all DDL (Screenshot1) Next issue is when I want to export teiid DDL from view model whose resultset columns contains a description. The description is generated twice. (project is in the attachments) The DDL looks like : {code:java} CREATE VIRTUAL PROCEDURE selfProc (stringIN string(4000)) RETURNS TABLE (result string(30) OPTIONS(ANNOTATION 'RS column description') OPTIONS(ANNOTATION 'RS column description')) AS BEGIN SELECT viewModel.selfProc.stringIN AS result; END; {code} Expected ddl: {code:java} CREATE VIRTUAL PROCEDURE selfProc (stringIN string(4000)) RETURNS TABLE (result string(30) OPTIONS(ANNOTATION 'RS column description')) AS BEGIN SELECT viewModel.selfProc.stringIN AS result; END; {code} > Need to add support for parsing OPTIONS in procedure statements > --------------------------------------------------------------- > > Key: TEIIDDES-2783 > URL: https://issues.jboss.org/browse/TEIIDDES-2783 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Dan Florian > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0 > > > The procedure DDL syntax supports OPTIONS() clause for procedure, parameter, result set, result set columns and datatype (RETURNS) clause. > CreateProcedureParser.parseReturnsClause() is not processing any OPTIONS() for procedure when RETURNS is just a datatype. See: https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL... > Should be able to parse the following and set the EMF *Description* (Annotation) value when imported into Designer > {code} > CREATE FOREIGN PROCEDURE ProcedureWithRS ( > newParameter_1 string(4000) OPTIONS(ANNOTATION 'parameter 1 description'), > newParameter_2 string(4000) > ) RETURNS string(255) OPTIONS(ANNOTATION 'Example') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 August 2016