October 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2742) Dataroles editor not updated when row filter added

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2742?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2742: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.3 (was: ) > Dataroles editor not updated when row filter added > -------------------------------------------------- > > Key: TEIIDDES-2742 > URL: https://issues.jboss.org/browse/TEIIDDES-2742 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 9.0.4, 10.0.1 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > > When adding Row Filter to a table, the list of filters is sometimes not updated. See Steps to reproduce for once such scenario. Closing the Data Role editor and reopening shows the correct row filters. > Also, in the Security column on the Model tab, the circle indicating a row filter is 'on' for the filter that does _not_ appear in the row filter list and is 'off' for the one that does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2838) Setting connection profile to imported model won't set data source (issues with Preview)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2838?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2838: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.3 (was: ) > Setting connection profile to imported model won't set data source (issues with Preview) > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-2838 > URL: https://issues.jboss.org/browse/TEIIDDES-2838 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > Attachments: Screen Shot 2016-05-09 at 16.35.06.png, Screen Shot 2016-05-09 at 16.54.45.png > > > I imported an existing project into TD with 2 source models and 1 view model. > After I set a connection profile to source model (via Modeling -> Set connection profile) it appears that Data Source is not set. As a result of this when I hit preview (Modeling -> Preview data) on some table in this model, it fails. Because the jndi-name in the dynamic vdb is set to null. > See screenshots > I am setting the priority to critical, because this used to work before. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2838) Setting connection profile to imported model won't set data source (issues with Preview)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2838?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2838. ---------------------------------- > Setting connection profile to imported model won't set data source (issues with Preview) > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-2838 > URL: https://issues.jboss.org/browse/TEIIDDES-2838 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > Attachments: Screen Shot 2016-05-09 at 16.35.06.png, Screen Shot 2016-05-09 at 16.54.45.png > > > I imported an existing project into TD with 2 source models and 1 view model. > After I set a connection profile to source model (via Modeling -> Set connection profile) it appears that Data Source is not set. As a result of this when I hit preview (Modeling -> Preview data) on some table in this model, it fails. Because the jndi-name in the dynamic vdb is set to null. > See screenshots > I am setting the priority to critical, because this used to work before. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2855) WSDL to Web Service model import doesn't work

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2855?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2855. ---------------------------------- > WSDL to Web Service model import doesn't work > --------------------------------------------- > > Key: TEIIDDES-2855 > URL: https://issues.jboss.org/browse/TEIIDDES-2855 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > Attachments: Hello.wsdl, Screen Shot 2016-06-15 at 10.32.34.png > > > When I hit context menu and then Import -> WSDL File or URL >> Web Service Model, select hello.wsdl (attached) and click next I get an error message saying: "The model descriptor must be supplied" (see screenshot) and I cannot continue. This works with TD 9.0.7. and doesn't work with TD 10.0.1.Beta1. > Is this an issue that is related to Web Service model deprecation ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2855) WSDL to Web Service model import doesn't work

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2855?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2855: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.3 (was: ) > WSDL to Web Service model import doesn't work > --------------------------------------------- > > Key: TEIIDDES-2855 > URL: https://issues.jboss.org/browse/TEIIDDES-2855 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes, verified_jbdsis-9.0.3 > Fix For: 10.0.2 > > Attachments: Hello.wsdl, Screen Shot 2016-06-15 at 10.32.34.png > > > When I hit context menu and then Import -> WSDL File or URL >> Web Service Model, select hello.wsdl (attached) and click next I get an error message saying: "The model descriptor must be supplied" (see screenshot) and I cannot continue. This works with TD 9.0.7. and doesn't work with TD 10.0.1.Beta1. > Is this an issue that is related to Web Service model deprecation ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ] Matej Kralik commented on TEIIDDES-2925: ---------------------------------------- ok, so when a user has the option to rename class name, the create materialized wizard should create tables in the JDG source model and name it according to the class name. However, when I set another name for class, tables in the JDG source model have set name according to view table which is materialized. Because of that, I have reopened this issue. For example, I have view table which will be materialized. Its name is 'viewAllBooks' # Right click on this table and choose Modeling > Materialized # Change class name from 'viewAllBooks' to 'Book' # Generated JDG tables have name : viewAllBooks AND ST_viewAllBooks1 (but should have Book and ST_Book1) I think that designer should do this when I create materialization or should show the warning that a user has to change the name of JDG source tables according to the class name. But I see another problem. When I have already created JDG source tables and set materialization, I have the option to generated POJO again (Right click to viewTable which is materialized (viewAllBooks) and Modeling>Create POJO). But what I change the class name again. How is use case ? Teiid designer should be rename JDG source tables which are already set according to new class name or at least show warning that user has to rename this tables? > Designer doesn't change java class name in the generated POJO module > -------------------------------------------------------------------- > > Key: TEIIDDES-2925 > URL: https://issues.jboss.org/browse/TEIIDDES-2925 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: screenshot1.png, screenshot2.png > > > I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-2925: ------------------------------------ > Designer doesn't change java class name in the generated POJO module > -------------------------------------------------------------------- > > Key: TEIIDDES-2925 > URL: https://issues.jboss.org/browse/TEIIDDES-2925 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: screenshot1.png, screenshot2.png > > > I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2942?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2942: ----------------------------------- Priority: Critical (was: Major) > Procedure input parameter has result in the generated DDL > --------------------------------------------------------- > > Key: TEIIDDES-2942 > URL: https://issues.jboss.org/browse/TEIIDDES-2942 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Priority: Critical > Attachments: ddlProject.zip > > > I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that: > {code:java} > TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52. > Procedure testProc RESULT param p1 must be of type OUT. > {code} > I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine. > Actual DDL: > {code:java} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} > expected DDL: > {code:java} > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2942) Procedure input parameter has result in the generated DDL

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-2942: -------------------------------------- Summary: Procedure input parameter has result in the generated DDL Key: TEIIDDES-2942 URL: https://issues.jboss.org/browse/TEIIDDES-2942 Project: Teiid Designer Issue Type: Bug Components: Dynamic VDBs Affects Versions: 10.0.2 Environment: Fedora 24 Reporter: Matej Kralik Attachments: ddlProject.zip I have a procedure with one input parameter. When I want to preview this procedure or deploy dynamic VDB, server shows me error that: {code:java} TEIID31100 Parsing error: Encountered "(4000) [*]result[*]) RETURNS" at line 2, column 52. Procedure testProc RESULT param p1 must be of type OUT. {code} I noticed that generated dynamic VDB contains 'result' in this parameter but this parameter has set direction to IN. When I delete the result from dynamic VDB, the procedure works fine. Actual DDL: {code:java} CREATE VIRTUAL PROCEDURE testProc (p1 string(4000) result) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') AS BEGIN SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; END; {code} expected DDL: {code:java} CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') AS BEGIN SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; END; {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2941) Provide an option to enforce that view column names match the sql transformation

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2941: ---------------------------------------- Summary: Provide an option to enforce that view column names match the sql transformation Key: TEIIDDES-2941 URL: https://issues.jboss.org/browse/TEIIDDES-2941 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Reporter: Steven Hawkins It is not required by the engine or the sql spec to have view column names match the column names of the projected query. But some users report changing the sql statement and expecting the view column order to change as well and that's not offered as an option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2016