July 2013 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1193?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1193. ------------------------------------ Resolution: Done This DB type is already supported on the Teiid side and is supported in Teiid Designer through the Teiid Connection DDL importer. > 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 > Assignee: Mark Drilling > Fix For: 8.2 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1557) Add Greenplum importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1557?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1557. ------------------------------------ Resolution: Done This DB type is already supported on the Teiid side and is supported in Teiid Designer through the Teiid Connection DDL importer. > Add Greenplum importer > ---------------------- > > Key: TEIIDDES-1557 > URL: https://issues.jboss.org/browse/TEIIDDES-1557 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2, Future > > > Add support for importing from a Greenplum data source. -- 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-883) Add support for Ingres database

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-883?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-883. ----------------------------------- Resolution: Done This DB type is already supported on the Teiid side and is supported in Teiid Designer through the Teiid Connection DDL importer. > Add support for Ingres database > ------------------------------- > > Key: TEIIDDES-883 > URL: https://issues.jboss.org/browse/TEIIDDES-883 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.3 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Labels: ingres > Fix For: 8.2 > > > For Ingres add support for > 1) Import of the metadata > 2) Creation of data source / Connection profile > 3) Export to DDL -- 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-904) Add JDBC import support for Intersystems Cache

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-904?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-904. ----------------------------------- Resolution: Done This DB type is already supported on the Teiid side and is supported in Teiid Designer through the Teiid Connection DDL importer. > Add JDBC import support for Intersystems Cache > ---------------------------------------------- > > Key: TEIIDDES-904 > URL: https://issues.jboss.org/browse/TEIIDDES-904 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Fix For: 8.2 > > > Please add JDBC import for Intersystems Cache database http://www.intersystems.com/cache/ -- 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-930) Add Support for Mondrian (OLAP)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-930?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-930. ----------------------------------- Resolution: Done This DB type is already supported on the Teiid side and is supported in Teiid Designer through the Teiid Connection DDL importer. > Add Support for Mondrian (OLAP) > ------------------------------- > > Key: TEIIDDES-930 > URL: https://issues.jboss.org/browse/TEIIDDES-930 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Fix For: 8.2 > > > Teiid 7.4 version adds a new OLAP Translator. This translator mimics more like File translator. Designer needs to add support for this translator. In order to use this translator supported procedure, Designer also need to support "arraytable", I think once the Designer libraries are upgraded to 7.4 this will be generally available. Until this JIRA is user can always hand model the procedure for OLAP source, which in the from > ResultSet invokeMDX(String mdxQuery) > The Resultset above should have a single column called "tuple" with data type "Object". During the runtime, this Object is really Object[] that can be used as below > select t.* from (call invokeMDX('query')) x, arraytable(x.tuple COLUMNS col1 string, col2 integer) t; -- 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-1387) Encountered NPE during XML Remote import

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1387?page=com.atlassian.jira.plu... ] Ted Jones edited comment on TEIIDDES-1387 at 7/15/13 3:50 PM: -------------------------------------------------------------- The ModelWorkspaceManager did not contain the newly created project when we tried to add the model resource since this happens when a resource is added. Changed to use ModelerCore.getWorkspace().getRoot().findMember(location) to get the project or project folder. Also broke logic out into a separate method in ModelerCore since this was needed in several classes for view and source models (XML, Flat File, Relational). was (Author: tejones): The ModelWorkspaceManager did not contain the newly created project when we tried to add the model resource since this happens when a resource is added. Changed to use ModelerCore.getWorkspace().getRoot().findMember(location) to get the project or project folder. Also broke logic out into a separate method in ModelErCore since this was needed in several classes for view and source models (XML, Flat File, Relational). > Encountered NPE during XML Remote import > ---------------------------------------- > > Key: TEIIDDES-1387 > URL: https://issues.jboss.org/browse/TEIIDDES-1387 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Mark Drilling > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.2 > > Attachments: PlantCatException.txt > > > Encountered NPE during import of the PlantCatalog remote XML file example - http://www.w3schools.com/xml/plant_catalog.xml > I think the issue was - I added the Plant child Elements, but left the 'root path' at the document root. However, when I re-tried the scenario - I didnt get the NPE again. Anyway, I am attaching the stacktrace - we may be able to figure out the issue from that. > This may be something we want to address for usability - maybe we can do some validation to ensure that the root path is appropriate for the selected elements? -- 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-1387) Encountered NPE during XML Remote import

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1387?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1387: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/204 > Encountered NPE during XML Remote import > ---------------------------------------- > > Key: TEIIDDES-1387 > URL: https://issues.jboss.org/browse/TEIIDDES-1387 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Mark Drilling > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.2 > > Attachments: PlantCatException.txt > > > Encountered NPE during import of the PlantCatalog remote XML file example - http://www.w3schools.com/xml/plant_catalog.xml > I think the issue was - I added the Plant child Elements, but left the 'root path' at the document root. However, when I re-tried the scenario - I didnt get the NPE again. Anyway, I am attaching the stacktrace - we may be able to figure out the issue from that. > This may be something we want to address for usability - maybe we can do some validation to ensure that the root path is appropriate for the selected elements? -- 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-1387) Encountered NPE during XML Remote import

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1387?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1387. --------------------------------- Resolution: Done The ModelWorkspaceManager did not contain the newly created project when we tried to add the model resource since this happens when a resource is added. Changed to use ModelerCore.getWorkspace().getRoot().findMember(location) to get the project or project folder. Also broke logic out into a separate method in ModelErCore since this was needed in several classes for view and source models (XML, Flat File, Relational). > Encountered NPE during XML Remote import > ---------------------------------------- > > Key: TEIIDDES-1387 > URL: https://issues.jboss.org/browse/TEIIDDES-1387 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Mark Drilling > Assignee: Ted Jones > Priority: Blocker > Fix For: 8.2 > > Attachments: PlantCatException.txt > > > Encountered NPE during import of the PlantCatalog remote XML file example - http://www.w3schools.com/xml/plant_catalog.xml > I think the issue was - I added the Plant child Elements, but left the 'root path' at the document root. However, when I re-tried the scenario - I didnt get the NPE again. Anyway, I am attaching the stacktrace - we may be able to figure out the issue from that. > This may be something we want to address for usability - maybe we can do some validation to ensure that the root path is appropriate for the selected elements? -- 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-1176) Usability Issue: On DDL importer, need better feed back when a file cannot be imported

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1176?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1176. ------------------------------------- Resolution: Done > Usability Issue: On DDL importer, need better feed back when a file cannot be imported > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-1176 > URL: https://issues.jboss.org/browse/TEIIDDES-1176 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: Testfile.ddl > > > When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed. > Also, 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-1176) Usability Issue: On DDL importer, need better feed back when a file cannot be imported

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1176?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1176: ----------------------------------------- Added messages for unhandled DDL statement types. The user is now given a message of the count and type of each unhandled statement, so that they have better feedback of which statements were skipped and why. https://github.com/Teiid-Designer/teiid-designer/pull/203 I am closing this issue and will open an enhancement request for the remaining work. > Usability Issue: On DDL importer, need better feed back when a file cannot be imported > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-1176 > URL: https://issues.jboss.org/browse/TEIIDDES-1176 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: Testfile.ddl > > > When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed. > Also, 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2013