December 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1066) Enable editing of the translator override when its being created, the name is not editable

by Van Halbert (JIRA)

Enable editing of the translator override when its being created, the name is not editable ------------------------------------------------------------------------------------------ Key: TEIIDDES-1066 URL: https://issues.jboss.org/browse/TEIIDDES-1066 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.4.2 Reporter: Van Halbert Building multiple vdb's in a single project, so that each will have different overrides to the translator in order to test various conditions. However, the translator override that is created for each vdb is called the same name (i.e,. <translator_name>-1), giving an illusion that properties maybe shared between the two. Unfortunately, was unable to change the name of the translator override so that each vdb override was specific. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1196) default criteria based on PK/FK relations should be included when adding tables to transformations

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1196?page=com.atlassian.jira.plu... ] Van Halbert moved JBEDSP-191 to TEIIDDES-1196: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-1196 (was: JBEDSP-191) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) > default criteria based on PK/FK relations should be included when adding tables to transformations > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1196 > URL: https://issues.jboss.org/browse/TEIIDDES-1196 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Priority: Optional > > Default transformation SQL when two tables with PK/FK relationship are joined (by pressing "add" button in Designer to add tables to transformation) should include default criteria specifying join on the PK/FK relationship. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDDES-303: ----------------------------------------- Sort of. If you develop a mat view model for external materialization that has a string length restriction that is inaccurate, and if you use the default generated create schema script, and you are using a database that doesn't automatically truncate, then this is still possible. However there is no issue with internal materialization and external materialization is not really considered a built-in process so this isn't necessarily an up-to-date issue. > Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model. > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-303 > URL: https://issues.jboss.org/browse/TEIIDDES-303 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Windows 2003 Server, 5.5 + patch 62 > Reporter: Michael Walker > Labels: materialization > > When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data. > This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail. > The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.

by Van Halbert (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ] Van Halbert commented on TEIIDDES-303: -------------------------------------- Is this still a possible issue? > Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model. > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-303 > URL: https://issues.jboss.org/browse/TEIIDDES-303 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Windows 2003 Server, 5.5 + patch 62 > Reporter: Michael Walker > Labels: materialization > > When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data. > This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail. > The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1154) Model Extension Definition (MED) Editor Does Not Reload When The MED File Was Changed On The File System From Outside The MED Editor

by Dan Florian (Created) (JIRA)

Model Extension Definition (MED) Editor Does Not Reload When The MED File Was Changed On The File System From Outside The MED Editor ------------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-1154 URL: https://issues.jboss.org/browse/TEIIDDES-1154 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 If the user uses a different editor, say the text editor, and the MED editor is open to the same file. The MED editor doesn't respond to the change that the file was changed. The user should be asked if they want to reload the editor using the changed MED file. I've already put code in the ResourceChangeLister of the MED Editor that catches this file change. I've also added a dialog to ask the user if they want to reload the editor. Both those changes have been comment out for now. The work left to do is refresh the editor GUI components and business objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1193) Add Hive importer

by Ramesh Reddy (Created) (JIRA)

Add Hive importer ----------------- Key: TEIIDDES-1193 URL: https://issues.jboss.org/browse/TEIIDDES-1193 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Ramesh Reddy Teiid 7.6, added Hive translator. The designer needs to add importer for the same. Note that even though Hive provides JBC driver, the metadata API is not upto date. So to get the list of tables, one needs to issue a call like show tables -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1184) Model Extension Property Definitions With Allowed Values But Without A Default Value Throw Exception In Properties View

by Dan Florian (Created) (JIRA)

Model Extension Property Definitions With Allowed Values But Without A Default Value Throw Exception In Properties View ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1184 URL: https://issues.jboss.org/browse/TEIIDDES-1184 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6, 7.7 If a MED has a property definition that has allowed values (like a boolean property type) but does not have a default value, Eclipse's Properties View cell editor throws an exception when trying to display the initial value (which is null/empty). Since the property definition was setup to have no default value there is not a value that can be returned to represent that since property's with allowed values must return an integer to the Properties View. Returning a -1 throws an IndexOutOfBoundesException and returning 0 (zero) will show the first allowed value but that is not what the property value really is. For 7.6 I recommend just returning the first value so that an exception is not thrown. For 7.7 we need to come up with a better solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] (TEIIDDES-1179) Source Tab Of MED Editor Does Not Set Header Title

by Dan Florian (Created) (JIRA)

Source Tab Of MED Editor Does Not Set Header Title -------------------------------------------------- Key: TEIIDDES-1179 URL: https://issues.jboss.org/browse/TEIIDDES-1179 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.6 Environment: Mac OS X 10.7.2 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 The header title of the source tab will be the title of the previously selected tab. The source tab should set its own title when it gets focus. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-321) Expression Builder in the Transformation Editor does not allow negative numeric constant values

by Barry LaFond (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-321?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-321: ---------------------------------- Fix Version/s: 7.7 Affects Version/s: 7.6 > Expression Builder in the Transformation Editor does not allow negative numeric constant values > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-321 > URL: https://issues.jboss.org/browse/TEIIDDES-321 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 7.6 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 7.7 > > Attachments: TEIIDDES-321.patch > > > Unable to input negative constant values into the expression editor. no errors or warnings occur when attempting. When pressing the hyphen key to input a negative, nothing is entered as a value. This affects TIMESTAMPADD() as an example. Without being able to enter a negative number, there is not a way to subtract from a date/time/timestamp value. > Workaround is to manually enter the negative value into the transformation SQL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1188) Provide ModeShape with example models and documentation for its task of updating the Teiid sequencers

by Van Halbert (Created) (JIRA)

Provide ModeShape with example models and documentation for its task of updating the Teiid sequencers ----------------------------------------------------------------------------------------------------- Key: TEIIDDES-1188 URL: https://issues.jboss.org/browse/TEIIDDES-1188 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.6 Reporter: Van Halbert Assignee: Barry LaFond Priority: Blocker ModeShape will need sample models and good documentation for what the new models look like and how the new extension property system is designed, so it can adequately know how to translate the extension properties into node types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2011