January 2016 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2355: ---------------------------------------- Need to test against a running Teiid instance with a back-end source with pushdown functions on it. > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2600) DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2600?page=com.atlassian.jira.plu... ] Work on TEIIDDES-2600 started by Barry LaFond. ---------------------------------------------- > DDL Importer does not yet support GLOBAL or LOCAL TEMP TABLE > ------------------------------------------------------------ > > Key: TEIIDDES-2600 > URL: https://issues.jboss.org/browse/TEIIDDES-2600 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, ModeShape Integration, Patch Release > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2.1 > > > Trying to import the following DDL into a View model (see: TEIIDDES-1794) the resulting Table has the Global Temp Table value set to *false*. > I don't think the TeiidDdlImporter is handling these particular cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ] Work on TEIIDDES-2355 started by Barry LaFond. ---------------------------------------------- > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2664) Add Model Extension support for Procedure RESULTS OPTIONS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2664?focusedWorklogId=12435333&p... ] Barry LaFond logged work on TEIIDDES-2664: ------------------------------------------ Author: Barry LaFond Created on: 12/Jan/16 10:21 AM Start Date: 12/Jan/16 10:21 AM Worklog Time Spent: 2 hours Work Description: Modeshape fix in place. Waiting on new jars to test in Designer Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours Worklog Id: (was: 12435333) > Add Model Extension support for Procedure RESULTS OPTIONS > --------------------------------------------------------- > > Key: TEIIDDES-2664 > URL: https://issues.jboss.org/browse/TEIIDDES-2664 > Project: Teiid Designer > Issue Type: Enhancement > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 9.2.1 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Teiid DDL now supports options for procedure/functions returns clause parameters: > ... RETURNS (options ...) type > ... RETURNS (options ...) TABLE (...) > This was added to Teiid version 8.12 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2664) Add Model Extension support for Procedure RESULTS OPTIONS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2664?page=com.atlassian.jira.plu... ] Work on TEIIDDES-2664 started by Barry LaFond. ---------------------------------------------- > Add Model Extension support for Procedure RESULTS OPTIONS > --------------------------------------------------------- > > Key: TEIIDDES-2664 > URL: https://issues.jboss.org/browse/TEIIDDES-2664 > Project: Teiid Designer > Issue Type: Enhancement > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 9.2.1 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Teiid DDL now supports options for procedure/functions returns clause parameters: > ... RETURNS (options ...) type > ... RETURNS (options ...) TABLE (...) > This was added to Teiid version 8.12 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2759) Missing translator after import

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2759: -------------------------------------- Summary: Missing translator after import Key: TEIIDDES-2759 URL: https://issues.jboss.org/browse/TEIIDDES-2759 Project: Teiid Designer Issue Type: Bug Affects Versions: 9.0.4 Reporter: Matus Makovy Attachments: QT_MySql50_Push.vdb Imported VDB has 2 Source models, one of them is missing a translator after import. Translator is specified in original vdb.xml included in TD vdb. {code:xml} <model visible="true" type="PHYSICAL" name="SP" path="/BQT_MySql/SP.xmi"> <property value="64600437" name="checksum"/> <property value="false" name="builtIn"/> <property value="2822882286.INDEX" name="indexName"/> <source translator-name="mysql5" connection-jndi-name="MySQL50_PushDS" name="SP"/> <validation-error path="sp_rows_between/ResultSet/BigIntegerValue" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_all_smalla_rows/ResultSet/DoubleNum" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_rows_between/ResultSet/BigDecimalValue" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_all_smalla_rows/ResultSet/BigDecimalValue" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_all_smalla_rows/ResultSet/FloatNum" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_rows_between/ResultSet/FloatNum" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_rows_between/ResultSet/DoubleNum" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> <validation-error path="sp_all_smalla_rows/ResultSet/BigIntegerValue" severity="WARNING">Missing or invalid Precision on column with a numeric datatype (See validation Preferences)</validation-error> </model> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger after import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2758?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2758: ----------------------------------- Affects Version/s: 9.0.4 > Change interger type to biginterger after import > ------------------------------------------------ > > Key: TEIIDDES-2758 > URL: https://issues.jboss.org/browse/TEIIDDES-2758 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: QT_MySql50_Push.vdb > > > Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger after import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2758?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2758: ----------------------------------- Attachment: QT_MySql50_Push.vdb > Change interger type to biginterger after import > ------------------------------------------------ > > Key: TEIIDDES-2758 > URL: https://issues.jboss.org/browse/TEIIDDES-2758 > Project: Teiid Designer > Issue Type: Bug > Reporter: Matus Makovy > Attachments: QT_MySql50_Push.vdb > > > Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger after import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2758?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2758: ---------------------------------------- I have a VDB that has around 70 errors in Problems view that are integer vs biginteger problems. > Change interger type to biginterger after import > ------------------------------------------------ > > Key: TEIIDDES-2758 > URL: https://issues.jboss.org/browse/TEIIDDES-2758 > Project: Teiid Designer > Issue Type: Bug > Reporter: Matus Makovy > > Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2758) Change interger type to biginterger after import

by Matus Makovy (JIRA)

Matus Makovy created TEIIDDES-2758: -------------------------------------- Summary: Change interger type to biginterger after import Key: TEIIDDES-2758 URL: https://issues.jboss.org/browse/TEIIDDES-2758 Project: Teiid Designer Issue Type: Bug Reporter: Matus Makovy Integer type was removed. After importing older VDB, TD complains about type incompatibility. Is there a possibility to check for integer in models after import and change it to biginterger? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2016