February 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2775) Provide automated way to convert a old functional model into relational model

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2775?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-2775: ------------------------------------- Assignee: Barry LaFond > Provide automated way to convert a old functional model into relational model > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2775 > URL: https://issues.jboss.org/browse/TEIIDDES-2775 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Reporter: Van Halbert > Assignee: Barry LaFond > > The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2775) Provide automated way to convert a old functional model into relational model

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2775?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2775: ---------------------------------- Summary: Provide automated way to convert a old functional model into relational model (was: Provide ability to convert a old functional model into relational model) > Provide automated way to convert a old functional model into relational model > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2775 > URL: https://issues.jboss.org/browse/TEIIDDES-2775 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Reporter: Van Halbert > > The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2775) Provide ability to convert a old functional model into relational model

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2775: ------------------------------------- Summary: Provide ability to convert a old functional model into relational model Key: TEIIDDES-2775 URL: https://issues.jboss.org/browse/TEIIDDES-2775 Project: Teiid Designer Issue Type: Feature Request Components: Modeling, Usability Reporter: Van Halbert The primary stipulation is that it will no longer be supported from a design time perspective the ability to create the function model. Consider offering option of an automated utility of some kind for this migration. There is a manual workaround, but for the user and usability, we should do this for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2774) Cannot extract model from imported VDB with same name

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2774: ---------------------------------------- Summary: Cannot extract model from imported VDB with same name Key: TEIIDDES-2774 URL: https://issues.jboss.org/browse/TEIIDDES-2774 Project: Teiid Designer Issue Type: Bug Components: Import/Export, VDB & Execution Affects Versions: 9.0.4 Reporter: Andrej Šmigala Attachments: extract_model.vdb After importing a VDB, the extract model Quick FIx is not available if the model has the same name as the VDB. Designer considers the VDB to be the same as the model, and offers to "synchronize" to model (which does nothing). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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... ] Barry LaFond updated TEIIDDES-2600: ----------------------------------- Fix Version/s: 10.0.1 > 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: 10.0.1, 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2427) Add Geometry Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2427?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2427: ----------------------------------- Fix Version/s: 10.0.1 > Add Geometry Type > ----------------- > > Key: TEIIDDES-2427 > URL: https://issues.jboss.org/browse/TEIIDDES-2427 > Project: Teiid Designer > Issue Type: Feature Request > Components: ModeShape Integration, Patch Release, Teiid Integration > Reporter: luca gioppo > Assignee: Barry LaFond > Labels: spatial, types > Fix For: 10.0.1, 9.2.1 > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > As part of TEIID-2384 a geometry type has been added to Teiid (blob + srid int) with associated system and pushdown logic. Designer should add support for the new type as well. We need to coordinate on the type uuid as that will bridge between Teiid and Designer. Currently Teiid just modified the blob identifier - https://github.com/teiid/teiid/blob/master/engine/src/main/resources/org/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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... ] Barry LaFond updated TEIIDDES-2664: ----------------------------------- Fix Version/s: 10.0.1 > 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: 10.0.1, 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-2748: ------------------------------------- This involves better, more complete handling of RPC style web services and will require significant changes to our schema and wsdl parsers to account for RPC as well as doc-lit. > ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2748 > URL: https://issues.jboss.org/browse/TEIIDDES-2748 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Minor > Fix For: 10.0.1, 9.2.1 > > > Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods. > On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected. > On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked. > On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation> > The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2152) Adding source table with quoted name results in wrong generated SQL statement

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2152?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2152. ------------------------------------ Resolution: Out of Date > Adding source table with quoted name results in wrong generated SQL statement > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2152 > URL: https://issues.jboss.org/browse/TEIIDDES-2152 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Transformations > Affects Versions: 8.5 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > > 1) Created source model with simple table named "My.Quoted.Table" (including quotes > 2) Created simple virtual table and pasted: SELECT * FROM "My.Quoted.Table" > 3) Parser returned a command resulting in the SQL: SELECT * FROM My.Quoted."Table" > Parser should be able to handle quoted names properly. In this case the SQL should have been valid as is. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2550) parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2550?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2550. ------------------------------------ Resolution: Done retested with 10.0.1 milestone. parses and validates OK > parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-2550 > URL: https://issues.jboss.org/browse/TEIIDDES-2550 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Patch Release, Transformations > Affects Versions: 9.1 > Environment: Teiid 8.7.1.redhat-8 and Teiid Designer 9.1.0.Beta1 > Reporter: Daan Creemers > Assignee: Paul Richardson > Fix For: 10.0.1, 9.2.1 > > Attachments: ParseTimestamp-Project.png, TestParseTimestamp.tar.gz > > > When using the parseTimestamp function in the transformation editor while creating a relational view model, a StringIndexOutOfBoundsException is thrown. The query SELECT parseTimestamp('18:10:20', 'HH:mm:ss') is used in the transformation editor which gives 'String index out of range: 1'. I want to use the function with a column of my table but produces the same error. > When deploying a virtual database and executing exactly the same query on the database, the query finishes successfully and gives the result. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 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 2016