February 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3037) Allow VDB user defined properties to have underscore(_) in the name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3037?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-4752 to TEIIDDES-3037: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-3037 (was: TEIID-4752) Component/s: (was: VDB) Affects Version/s: (was: 8.12.5) > Allow VDB user defined properties to have underscore(_) in the name > ------------------------------------------------------------------- > > Key: TEIIDDES-3037 > URL: https://issues.jboss.org/browse/TEIIDDES-3037 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Chandra Akkinepalli > Assignee: Barry LaFond > Priority: Minor > > VDB's userdefined properties doesn't allow Names containing underscore in them. > Our naming standards are defined to have _ in them. This is preventing us from doing a update via designer. As a work around we are udpating vdb.xml file within .vdb in an offline manner. > It would would be great if this restriction can be removed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3024) Import/Export ddl problem with Indexes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3024?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3024: ----------------------------------- Fix Version/s: 11.1 (was: 11.0.1) > Import/Export ddl problem with Indexes > --------------------------------------- > > Key: TEIIDDES-3024 > URL: https://issues.jboss.org/browse/TEIIDDES-3024 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Fix For: 11.1 > > Attachments: verification.zip > > > According this : [DDL metadata|https://docs.jboss.org/author/display/TEIID/DDL+Metadata] > Index should look like this: > CONSTRAINT EXAMPLE_INDEX INDEX (name, amount) > but in our ddl look: > newColumn_1 string(4000) INDEX > Problem is that when we export and import source model new model have two indexes with the same default name INDEX(colision/error) and also there are missing atributes Name In Source and description. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3036) Create POJO doesn't generate anything when one of the columns has a column type biginteger

by Cojan van Ballegooijen (JIRA)

Cojan van Ballegooijen created TEIIDDES-3036: ------------------------------------------------ Summary: Create POJO doesn't generate anything when one of the columns has a column type biginteger Key: TEIIDDES-3036 URL: https://issues.jboss.org/browse/TEIIDDES-3036 Project: Teiid Designer Issue Type: Bug Environment: JBoss Developer Studio 9.1.0 with Teiid Designer 10.0.2 installed Reporter: Cojan van Ballegooijen Attachments: Screen Shot 2017-02-09 at 12.02.56.png Creating a POJO from a source model table doesn't generate the classes and module zip file when one of the columns has a datatype biginteger. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

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

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2783. ---------------------------------- > 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 > Fix For: 11.0.1 > > Attachments: 1.png, 2.png, 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 (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

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

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2783: ----------------------------------- Labels: release_notes (was: ) > 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 > Fix For: 11.0.1 > > Attachments: 1.png, 2.png, 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 (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3035) Create POJO option create .java source files with ^M

by Cojan van Ballegooijen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3035?page=com.atlassian.jira.plu... ] Cojan van Ballegooijen updated TEIIDDES-3035: --------------------------------------------- Attachment: Product_JDG_Module.zip > Create POJO option create .java source files with ^M > ----------------------------------------------------- > > Key: TEIIDDES-3035 > URL: https://issues.jboss.org/browse/TEIIDDES-3035 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Modeling > Affects Versions: 10.0.2 > Environment: JBoss Developer Studion 9.1 with the latest supported Integration Stack installed. > Reporter: Cojan van Ballegooijen > Priority: Minor > Attachments: Product_JDG_Module.zip > > > The Create POJO option on a model generate java files with ^M on each line. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3035) Create POJO option create .java source files with ^M

by Cojan van Ballegooijen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3035?page=com.atlassian.jira.plu... ] Cojan van Ballegooijen updated TEIIDDES-3035: --------------------------------------------- Steps to Reproduce: - File -> New -> Teiid Model Project - File -> New -> Teiid Meta model with model class Relational with model type Source Model - New -> Child -> Table Add some columns - Right Click on the new create model and select Create POJO Check Generate JDG Module as well You will see that the generated java source files contains a ^M on each line using VI. was: - File -> New -> Teiid Model Project - File -> New -> Teiid Meta model with model class Relational with model type Source Model - New -> Child -> Table Add some columns - Right Click on the new create model and select Create POJO Check Generate JDG Module as well You will see that the generated java source files contains a ^M on each line. > Create POJO option create .java source files with ^M > ----------------------------------------------------- > > Key: TEIIDDES-3035 > URL: https://issues.jboss.org/browse/TEIIDDES-3035 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Modeling > Affects Versions: 10.0.2 > Environment: JBoss Developer Studion 9.1 with the latest supported Integration Stack installed. > Reporter: Cojan van Ballegooijen > Priority: Minor > Attachments: Product_JDG_Module.zip > > > The Create POJO option on a model generate java files with ^M on each line. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3035) Create POJO option create .java source files with ^M

by Cojan van Ballegooijen (JIRA)

Cojan van Ballegooijen created TEIIDDES-3035: ------------------------------------------------ Summary: Create POJO option create .java source files with ^M Key: TEIIDDES-3035 URL: https://issues.jboss.org/browse/TEIIDDES-3035 Project: Teiid Designer Issue Type: Bug Components: Dialogs, Modeling Affects Versions: 10.0.2 Environment: JBoss Developer Studion 9.1 with the latest supported Integration Stack installed. Reporter: Cojan van Ballegooijen Priority: Minor The Create POJO option on a model generate java files with ^M on each line. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2783?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2783. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/135b7b917db5f4f7d... Marking this issue as resolved, but opened TEIIDDES-3034 to cover related procedure result set issue > 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 > Fix For: 11.0.1 > > Attachments: 1.png, 2.png, 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 (v7.2.3#72005)

7 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 > 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 > > > 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.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2017