July 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1425) Refactor > Rename of abstraction layer model was partially reflected in transformation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1425?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1425. ------------------------------------ Resolution: Out of Date The refactoring of Designer's refactor framework included an improvement to the SQL text logic in RefactorResourceUtils.calculateSQLChanges() method. Out of date and fixed > Refactor > Rename of abstraction layer model was partially reflected in transformation > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-1425 > URL: https://issues.jboss.org/browse/TEIIDDES-1425 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7.1 > Environment: JBDS 5.0 GA, SOA-tooling CR1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.2 > > Attachments: RefactorRename_MPS.zip > > > This project had a source model, abstraction layer (transformed from source), and a view model with a transformation. The transformation is essentially: > SELECT * FROM vParts.Supplier AS s, vParts.Supplier_parts AS sp WHERE s.Supplier_id = sp.Supplier_id > I added a second source and then used Refactor > Rename to change the original abstraction layer model from vParts to vParts_Oracle. > The transformation was altered like this: > SELECT * FROM vParts_Oracle.Supplier AS s, vParts.Supplier_parts AS sp WHERE s.Supplier_id = sp.Supplier_id > So, it changed only the first instance of the model, leaving the transformation invalid. > I'll attach a Model Project Set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1783) Import of Oracle DDL with indexes does not create them

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1783?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1783. ------------------------------------- Resolution: Done OracleImporter was looking for the incorrect DDL Index statement - corrected. Also added processing for setting the index column references. https://github.com/Teiid-Designer/teiid-designer/pull/202 > Import of Oracle DDL with indexes does not create them > ------------------------------------------------------ > > Key: TEIIDDES-1783 > URL: https://issues.jboss.org/browse/TEIIDDES-1783 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > Import of Oracle DDL with index statements via the DDL importer does not create any indexes in the generated model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1783) Import of Oracle DDL with indexes does not create them

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1783: --------------------------------------- Summary: Import of Oracle DDL with indexes does not create them Key: TEIIDDES-1783 URL: https://issues.jboss.org/browse/TEIIDDES-1783 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.2 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.2 Import of Oracle DDL with index statements via the DDL importer does not create any indexes in the generated model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1778) Change the Teiid Server version in the preferences to 8.4

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1778?page=com.atlassian.jira.plu... ] Paul Richardson updated TEIIDDES-1778: -------------------------------------- Attachment: teiid-default-server-version.png Attached a screenshot of a new workspace with a nightly install. As can be seen, the default server preference is empty and thus the server version is 8.0.0 (the last resort default). I have updated the last resort default to 8.4.0 but I cannot work out how 8.3.x could be the default server version. > Change the Teiid Server version in the preferences to 8.4 > --------------------------------------------------------- > > Key: TEIIDDES-1778 > URL: https://issues.jboss.org/browse/TEIIDDES-1778 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Attachments: teiid-default-server-version.png > > > The Teiid Designer preference for Teiid Server version is defaulting to 8.3, this should be 8.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1782) DDL import wizard - add better control over selection of imported objects

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1782: --------------------------------------- Summary: DDL import wizard - add better control over selection of imported objects Key: TEIIDDES-1782 URL: https://issues.jboss.org/browse/TEIIDDES-1782 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 8.2 Reporter: Mark Drilling Fix For: 8.3 User request to provide better control over which object types are imported via the DDL importer: It would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1725) As default behavior, Importing DDL into an existing model removed the other tables

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1725?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1725. ------------------------------------- Resolution: Done Marking this one complete - the differences page has changed in the rework of the importer. > As default behavior, Importing DDL into an existing model removed the other tables > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1725 > URL: https://issues.jboss.org/browse/TEIIDDES-1725 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > > When using the DDL importer to import into an existing model, the default behavior is to replace what's there, not just add to an existing model. I think the default behavior should be do no harm, which would be add to the existing model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1674) DDL Importer - does not handle extension properties

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1674. ------------------------------------- Resolution: Done Added warning dialog to inform user when extension properties exist, but cannot be processed. https://github.com/Teiid-Designer/teiid-designer/pull/201 > DDL Importer - does not handle extension properties > --------------------------------------------------- > > Key: TEIIDDES-1674 > URL: https://issues.jboss.org/browse/TEIIDDES-1674 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.2 > > > The DDL Importer currently does not fully support import of Function Procedures from Teiid DDL. An example: > CREATE VIRTUAL FUNCTION F4( > flag boolean, > msg varchar > ) RETURNS varchar > OPTIONS ( > CATEGORY 'misc', > DETERMINISM 'DETERMINISTIC', > "NULL-ON-NULL" 'true', > JAVA_CLASS 'foo', > JAVA_METHOD 'bar' > ); > The current DDL Importer cannot easily set properties which are implemented as extension properties. Examples are CATEGORY, JAVA_CLASS, JAVA_METHOD in the above example. > We should look into re-working the DDL Importer to use Barry's framework for creating relational objects. I believe that framework has built in support for the extension properties. > Importing for Salesforce connection will also not work, nor a simple DB where Native Query values are set on tables -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1781) Need to Create Built-in MED for OData

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1781: ----------------------------------- Summary: Need to Create Built-in MED for OData Key: TEIIDDES-1781 URL: https://issues.jboss.org/browse/TEIIDDES-1781 Project: Teiid Designer Issue Type: Task Components: Extension Framework Affects Versions: 8.2 Reporter: Ted Jones Assignee: Mark Drilling Fix For: 8.2 Need to create a MED to support OData specific datatypes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1778) Change the Teiid Server version in the preferences to 8.4

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1778?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1778: --------------------------------------- Yes, this was a clean keplar install with the latest 8.2 nightly of Designer. > Change the Teiid Server version in the preferences to 8.4 > --------------------------------------------------------- > > Key: TEIIDDES-1778 > URL: https://issues.jboss.org/browse/TEIIDDES-1778 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > > The Teiid Designer preference for Teiid Server version is defaulting to 8.3, this should be 8.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1778) Change the Teiid Server version in the preferences to 8.4

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1778?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1778: ------------------------------------------- Van, Can you be more specific about the preference, ie. is the actual value of Window > Preferences > Teiid Designer > Default Server Version set to "8.3.x"? Is this a clean workspace that you have not set the preference on before? Reasons for asking: * A clean workspace has no preference set at all with the last-resort default server version set to 8.0.0 (which I have now amended to 8.4.0) * Once the preference is set, it is stored in the workspace and reflects a decision by the user hence should not be updated > Change the Teiid Server version in the preferences to 8.4 > --------------------------------------------------------- > > Key: TEIIDDES-1778 > URL: https://issues.jboss.org/browse/TEIIDDES-1778 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > > The Teiid Designer preference for Teiid Server version is defaulting to 8.3, this should be 8.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013