February 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2441) Problems with dialogs in constrained resolutions

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2441: ---------------------------------------- Summary: Problems with dialogs in constrained resolutions Key: TEIIDDES-2441 URL: https://issues.jboss.org/browse/TEIIDDES-2441 Project: Teiid Designer Issue Type: Quality Risk Components: Dialogs Affects Versions: 8.0 Reporter: Steven Hawkins When working with a small resolution, such as 800x600, many dialogs seem to cutoff critical controls such that cannot be resized and progress cannot be made. This has been observed with the vdb editor not showing the roles editor and the web service creation dialog not being able to make progress. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model

by Endy Brosens (JIRA)

Endy Brosens created TEIIDDES-2440: -------------------------------------- Summary: No proper column mapping for second primary key in view model Key: TEIIDDES-2440 URL: https://issues.jboss.org/browse/TEIIDDES-2440 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.6, 8.3.4 Environment: Windows Reporter: Endy Brosens I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined. I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys. I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with. This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows. The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2439: ----------------------------------- Assignee: Ted Jones > Import from JSON error not helpful > ---------------------------------- > > Key: TEIIDDES-2439 > URL: https://issues.jboss.org/browse/TEIIDDES-2439 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 9.1 > > > When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2439: -------------------------------- Fix Version/s: 9.1 > Import from JSON error not helpful > ---------------------------------- > > Key: TEIIDDES-2439 > URL: https://issues.jboss.org/browse/TEIIDDES-2439 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 9.1 > > > When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2438) Deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, one with integer field

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2438?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2438: ----------------------------------- Priority: Major (was: Minor) > Deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, one with integer field > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2438 > URL: https://issues.jboss.org/browse/TEIIDDES-2438 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 9.0.1 > Environment: Centos 6.5, JBoss EAP 6.3 alpha1, Teiid 8.9.1 > Fedora 21, Eclipse 4.4, Teiid Designer 9.0.1 > Reporter: Leslie Mann > > Receiving a deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, other with integer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2439: ---------------------------------------- Summary: Import from JSON error not helpful Key: TEIIDDES-2439 URL: https://issues.jboss.org/browse/TEIIDDES-2439 Project: Teiid Designer Issue Type: Quality Risk Components: Import/Export Reporter: Steven Hawkins When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2438) Deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, one with integer field

by Leslie Mann (JIRA)

Leslie Mann created TEIIDDES-2438: ------------------------------------- Summary: Deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, one with integer field Key: TEIIDDES-2438 URL: https://issues.jboss.org/browse/TEIIDDES-2438 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 9.0.1 Environment: Centos 6.5, JBoss EAP 6.3 alpha1, Teiid 8.9.1 Fedora 21, Eclipse 4.4, Teiid Designer 9.0.1 Reporter: Leslie Mann Priority: Minor Receiving a deploy error "expected integer, but was biginteger" when VDB table has definition consisting of union of two tables, one with int field, other with integer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2437) Enable specifying VDB Version when using VDB RE-USE feature

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2437: ------------------------------------- Summary: Enable specifying VDB Version when using VDB RE-USE feature Key: TEIIDDES-2437 URL: https://issues.jboss.org/browse/TEIIDDES-2437 Project: Teiid Designer Issue Type: Enhancement Components: VDB & Execution Affects Versions: 9.0.1 Reporter: Van Halbert Assignee: Barry LaFond Priority: Critical When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2436: ----------------------------------- Priority: Critical (was: Major) > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.1, 9.0.2 > > Attachments: JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2436: ----------------------------------- Fix Version/s: 9.1 9.0.2 > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.1, 9.0.2 > > Attachments: JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2015