December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3154) Index keys not created for quoted columns names

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3154?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3154: ----------------------------------- Labels: release_notes (was: ) > Index keys not created for quoted columns names > ----------------------------------------------- > > Key: TEIIDDES-3154 > URL: https://issues.jboss.org/browse/TEIIDDES-3154 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes > Fix For: 11.1.1 > > > If table has a columns like > CREATE FOREIGN TABLE Blah ( > id int, > "year" date, > PRIMARY KEY ("year") > ); > Then during the metadata import process, the PK is ignored. Also test same scenario for UNIQUE KEY and FOREIGN KEY. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3146) Teiid Execution plan locks up Teiid Designer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3146?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3146. ---------------------------------- > Teiid Execution plan locks up Teiid Designer > -------------------------------------------- > > Key: TEIIDDES-3146 > URL: https://issues.jboss.org/browse/TEIIDDES-3146 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 11.1 > Environment: JBoss Developer Studio 11 with Teiid Designer 11.1 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes > Fix For: 11.1.1 > > Attachments: lockup.mkv, preview-data-input-dialog.png > > > Previewing data on any datasource that is not relational (file, excel, REST, etc) will produce a delay as the Teiid Execution Plan is calculated. During calculation, the entire Teiid Designer workspace is locked. When calculating execution plans on more than one datasource this delay can take several minutes. The designer is completely unusable while calculating -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3146) Teiid Execution plan locks up Teiid Designer

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3146?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3146: ----------------------------------- Labels: release_notes (was: ) > Teiid Execution plan locks up Teiid Designer > -------------------------------------------- > > Key: TEIIDDES-3146 > URL: https://issues.jboss.org/browse/TEIIDDES-3146 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 11.1 > Environment: JBoss Developer Studio 11 with Teiid Designer 11.1 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Labels: release_notes > Fix For: 11.1.1 > > Attachments: lockup.mkv, preview-data-input-dialog.png > > > Previewing data on any datasource that is not relational (file, excel, REST, etc) will produce a delay as the Teiid Execution Plan is calculated. During calculation, the entire Teiid Designer workspace is locked. When calculating execution plans on more than one datasource this delay can take several minutes. The designer is completely unusable while calculating -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3152. ---------------------------------- > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.1.1 > > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3152) VDB does not have MXD based properties

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3152?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3152: ----------------------------------- Labels: release_notes (was: ) > VDB does not have MXD based properties > -------------------------------------- > > Key: TEIIDDES-3152 > URL: https://issues.jboss.org/browse/TEIIDDES-3152 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.1.1 > > Attachments: sample.ddl > > > After adding a custom MXD (see TEIIDDES-3151), if you import a DDL that makes use of the MXD properties, the model will show the properties in "Extensions" in left side panel. However, when creating a .vdb or dynamic VDB these properties not exported at all in the resulting VDB > Attached a sample DDL file, but same would apply if I use Teiid Connection Importer too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3167) Teiid Connection Import - The deployment timeout once edited will not work

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-3167: -------------------------------------- Summary: Teiid Connection Import - The deployment timeout once edited will not work Key: TEIIDDES-3167 URL: https://issues.jboss.org/browse/TEIIDDES-3167 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Ramesh Reddy Using Teiid Designer 11.1 version (did not test older versions), during the import process using the Teiid Connection importer, if you change the default timeout property from 120 to any value (on the advanced tab) from there on any teiid connection importer deployments will fail with timeout. Even setting back to 120 will not work. I feel the code somewhere may be interpreting the value as milliseconds instead of seconds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2865: ---------------------------------------- [~mkralik] looking at Teiid's code (JDBCMetadataProcessor.java) I'm seeing the following: column.setPrecision(columnSize); column.setScale(scale); //assume that null means 0 column.setLength(columnSize); so column size is set for both precision and length In Designer's RelationalModelProcessor.java, we're setting: column.setLength(columnSize); however, precision isn't being set to columnSize unless it's a numeric Runtime type. I'm going remove that logic to match Teiid runtime's logic. > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2865 > URL: https://issues.jboss.org/browse/TEIIDDES-2865 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1, 11.1.1 > > Attachments: debTest2Import.png, debtestImport.png, importedColumns.png > > > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly. > You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds > user - mss_eds > password - mss_eds > table - debtest2, both columns are numeric(9,2) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3153. ---------------------------------- > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions > ** set required properties > * In primary Model Editor tab for the source model > ** Select *Export Teiid DDL* and verify the DDL contains the OPTIONS() properties and the SET NAMESPACE statement > ** Select a table and click the generate data service (vdb.xml) toolbar button (bottom). Verify OPTIONS() and SET NAMESPACE are there > * Create a VDB containing the source model and open VDB Editor > ** Select *Save As XML* button and verify OPTIONS() and SET NAMESPACE are in the generated *.vdb.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3153) Fix various Model Extension issues with import/export DDL and vdb.xml formats

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3153?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3153: ----------------------------------- Labels: release_notes (was: ) > Fix various Model Extension issues with import/export DDL and vdb.xml formats > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3153 > URL: https://issues.jboss.org/browse/TEIIDDES-3153 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1.1 > > Attachments: my_custom_med.mxd > > > Current 11.1 Designer does not fully support import/export DDL and vdb.xml containing model extension properties, especially user's custom/logcal model extension definitions (*.mxd files) > Applicable actions > Model Explorer > * Select source model with table and procedure and apply custom MED via Modeling >> Manage Model Extension Definitions > ** set required properties > * In primary Model Editor tab for the source model > ** Select *Export Teiid DDL* and verify the DDL contains the OPTIONS() properties and the SET NAMESPACE statement > ** Select a table and click the generate data service (vdb.xml) toolbar button (bottom). Verify OPTIONS() and SET NAMESPACE are there > * Create a VDB containing the source model and open VDB Editor > ** Select *Save As XML* button and verify OPTIONS() and SET NAMESPACE are in the generated *.vdb.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3136) PK's are not imported from JDBC source when import FK's is turned off

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3136?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3136: ----------------------------------- Labels: release_notes (was: ) > PK's are not imported from JDBC source when import FK's is turned off > ---------------------------------------------------------------------- > > Key: TEIIDDES-3136 > URL: https://issues.jboss.org/browse/TEIIDDES-3136 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1.1 > > > If Import FK's is turned OFF (unchecked) then PK's are not imported as part of the table schema. > RelationalModelProcessorImpl.createPrimaryKey() method is checking for includeFKs & includeInexes options and returning if both are false. Need to remove this check and let PK's be imported either way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017