March 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2808) native-type and native-query extension properties aren't saving values entered in properties view

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2808: -------------------------------------- Summary: native-type and native-query extension properties aren't saving values entered in properties view Key: TEIIDDES-2808 URL: https://issues.jboss.org/browse/TEIIDDES-2808 Project: Teiid Designer Issue Type: Bug Components: Patch Release Affects Versions: 9.0.5 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 9.0.6 The fix for these was included in 10.x branch via TEIIDDES-2700, but was requested for 9.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2355) Provide an option to import pushdown functions

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2355: ---------------------------------------- [~blafond] I've created a function in Oracle 11 DB: {code:sql} CREATE OR REPLACE FUNCTION get_edition(ISBNI IN VARCHAR2) RETURN NUMBER IS editionr NUMBER(1); BEGIN SELECT edition INTO editionr FROM books WHERE isbn = isbni; RETURN(editionr); END; {code} Then I've tried to import from this DB using Teiid Connection Import with "Import Procedures" property set to "true" This is the generated DDL: {code:sql} CREATE FOREIGN PROCEDURE GET_EDITION(OUT "return" bigdecimal(22) RESULT OPTIONS (NATIVE_TYPE 'NUMBER'), IN ISBNI string OPTIONS (NATIVE_TYPE 'VARCHAR2')) OPTIONS (NAMEINSOURCE '"GET_EDITION"') {code} > Provide an option to import pushdown functions > ---------------------------------------------- > > Key: TEIIDDES-2355 > URL: https://issues.jboss.org/browse/TEIIDDES-2355 > Project: Teiid Designer > Issue Type: Feature Request > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 9.2.1 > > > The import property importer.importPushdownFunctions can be set to have Teiid include the pushdown functions as part of the imported schema and there by the ddl used by designer. With TEIID-3098 will prevent there from being ambiguity from doing so (either from multiple models or from the pushdown functions). So Designer should allow users to import these functions if they wish (it could even be a default option). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2807) Automatic propagation of meta-model changes

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2807?page=com.atlassian.jira.plu... ] Steve Tran updated TEIIDDES-2807: --------------------------------- Description: It would be nice if changes in meta models would automatically propagate to dependent layers. For example, I update my datasource XMI so that a column has been added. In my base layer, the select query was "select * from XYZ". The meta model is not updated with the new column from the datasource XMI until I trigger JBDS to rebuild the workspace by adding a random space character in the "select * from XYZ" statement and pressing save. In cases where the select statement is not select *, it should do nothing since the user has explicitly defined the select. (was: When starting jDV/EAP within JBDS, a non-fatal error is thrown every time. It can be ignored, but it's an annoyance that customers have reported.) > Automatic propagation of meta-model changes > ------------------------------------------- > > Key: TEIIDDES-2807 > URL: https://issues.jboss.org/browse/TEIIDDES-2807 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 9.0.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Minor > > It would be nice if changes in meta models would automatically propagate to dependent layers. For example, I update my datasource XMI so that a column has been added. In my base layer, the select query was "select * from XYZ". The meta model is not updated with the new column from the datasource XMI until I trigger JBDS to rebuild the workspace by adding a random space character in the "select * from XYZ" statement and pressing save. In cases where the select statement is not select *, it should do nothing since the user has explicitly defined the select. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2807) Automatic propagation of meta-model changes

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2807?page=com.atlassian.jira.plu... ] Steve Tran updated TEIIDDES-2807: --------------------------------- Issue Type: Feature Request (was: Bug) > Automatic propagation of meta-model changes > ------------------------------------------- > > Key: TEIIDDES-2807 > URL: https://issues.jboss.org/browse/TEIIDDES-2807 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 9.0.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Minor > > When starting jDV/EAP within JBDS, a non-fatal error is thrown every time. It can be ignored, but it's an annoyance that customers have reported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2807) Automatic propagation of meta-model changes

by Steve Tran (JIRA)

Steve Tran created TEIIDDES-2807: ------------------------------------ Summary: Automatic propagation of meta-model changes Key: TEIIDDES-2807 URL: https://issues.jboss.org/browse/TEIIDDES-2807 Project: Teiid Designer Issue Type: Bug Affects Versions: 9.0.3 Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 64-bit Windows 7 environment Reporter: Steve Tran Assignee: Barry LaFond Priority: Minor When starting jDV/EAP within JBDS, a non-fatal error is thrown every time. It can be ignored, but it's an annoyance that customers have reported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2693) Allow warnings to be presented to the user when importing from JDBC

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2693?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2693: -------------------------------------- Assignee: Barry LaFond > Allow warnings to be presented to the user when importing from JDBC > ------------------------------------------------------------------- > > Key: TEIIDDES-2693 > URL: https://issues.jboss.org/browse/TEIIDDES-2693 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 10.0.2 > > > This came up when resolving TEIIDDES-2458. The fix attempts to get the correct name in source for the sybase tables, but there's a possibility this will fail. We still want to finish the import, but we'd also like to warn the user the NIS might be incorrect. > See the comment in this PR: https://github.com/Teiid-Designer/teiid-designer/pull/516 > <blafond> asmigala: oops. missed it. Since this warning would probably occur on multiple tables/columns it wouldn't be good to pop up a dialog during the processing. > <blafond> asmigala: If we added an IStatus[] to RelationalModelProcessorImpl, we could check it's Severity and throw up a Warning/Error summary dialog after processing? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2724) [Usability] Importing DDL that has unsupported syntax is not indicated in error message

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2724?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2724: -------------------------------------- Assignee: Dan Florian > [Usability] Importing DDL that has unsupported syntax is not indicated in error message > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2724 > URL: https://issues.jboss.org/browse/TEIIDDES-2724 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0.3 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 10.0.2 > > > Importing DDL that contains unsupported syntax produces the following "Import Messages": > - 2 instances of a DDL statement of type [ddl:ddlProblem] were found, but cannot be processed > This message doesn't give any indication as to which statement (s) are the issue. And didn't find any message(s) in the .log file either. It would be better if "ddl:ddlProblem" was replaced with the first "x" number of characters from the statement that was identified as a problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2724) [Usability] Importing DDL that has unsupported syntax is not indicated in error message

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2724?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2724: ----------------------------------- Component/s: ModeShape Integration > [Usability] Importing DDL that has unsupported syntax is not indicated in error message > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2724 > URL: https://issues.jboss.org/browse/TEIIDDES-2724 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, ModeShape Integration > Affects Versions: 9.0.3 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 10.0.2 > > > Importing DDL that contains unsupported syntax produces the following "Import Messages": > - 2 instances of a DDL statement of type [ddl:ddlProblem] were found, but cannot be processed > This message doesn't give any indication as to which statement (s) are the issue. And didn't find any message(s) in the .log file either. It would be better if "ddl:ddlProblem" was replaced with the first "x" number of characters from the statement that was identified as a problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2806) Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2806?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2806: ----------------------------------- Fix Version/s: 10.0.2 > Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2806 > URL: https://issues.jboss.org/browse/TEIIDDES-2806 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dynamic VDBs > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.2 > > > The Teiid vdb has column named e.g. PE$HOME. When I generate a dynamic vdb xml from this model, the xml document contains: > CREATE FOREIGN TABLE MYTABLE ( > ID string(40) NOT NULL, > NAME string(40), > PE$HOME string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > When i deploy this, it fails because P$HOME is not allowed as column name. > I expect to see this name "quoted" in the xml vdb: > CREATE FOREIGN TABLE MYTABLE ( > "ID" string(40) NOT NULL, > "NAME" string(40), > "PE$HOME" string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > Proposed solution: always use "quotes" in source and view xml vdb, both for the column names, and the mapping statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2806) Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2806?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2806: ----------------------------------- Component/s: Patch Release > Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2806 > URL: https://issues.jboss.org/browse/TEIIDDES-2806 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dynamic VDBs, Patch Release > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.2 > > > The Teiid vdb has column named e.g. PE$HOME. When I generate a dynamic vdb xml from this model, the xml document contains: > CREATE FOREIGN TABLE MYTABLE ( > ID string(40) NOT NULL, > NAME string(40), > PE$HOME string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > When i deploy this, it fails because P$HOME is not allowed as column name. > I expect to see this name "quoted" in the xml vdb: > CREATE FOREIGN TABLE MYTABLE ( > "ID" string(40) NOT NULL, > "NAME" string(40), > "PE$HOME" string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > Proposed solution: always use "quotes" in source and view xml vdb, both for the column names, and the mapping statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016