June 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1739) Refactor DdlImporter into dialect-specific processors.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1739?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1739: -------------------------------------- Assignee: Paul Richardson > Refactor DdlImporter into dialect-specific processors. > ------------------------------------------------------ > > Key: TEIIDDES-1739 > URL: https://issues.jboss.org/browse/TEIIDDES-1739 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2 > > > Current DdlImporter handles multiple DDL dialects, including the new Teiid-related modifications. > Refactor this class to allow dialect-specific implementations of an Interface that can be handed an AstNode and either process the node, or not. > Also need to allow for handing off Teiid-DDL Options to the Extension Assistants to inject the extension properties into the models. This is currently not handled correctly -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1739) Refactor DdlImporter into dialect-specific processors.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1739?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1739: ----------------------------------- Priority: Blocker (was: Major) > Refactor DdlImporter into dialect-specific processors. > ------------------------------------------------------ > > Key: TEIIDDES-1739 > URL: https://issues.jboss.org/browse/TEIIDDES-1739 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.2 > > > Current DdlImporter handles multiple DDL dialects, including the new Teiid-related modifications. > Refactor this class to allow dialect-specific implementations of an Interface that can be handed an AstNode and either process the node, or not. > Also need to allow for handing off Teiid-DDL Options to the Extension Assistants to inject the extension properties into the models. This is currently not handled correctly -- 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, 6 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1674: -------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) > 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, 6 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1674: -------------------------------------- Assignee: Paul Richardson > 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: Paul Richardson > 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, 6 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1674?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1674: ----------------------------------- Priority: Blocker (was: Major) > 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 > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1706) During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1706?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1706: ----------------------------------- Priority: Blocker (was: Major) > During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1706 > URL: https://issues.jboss.org/browse/TEIIDDES-1706 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.2 > > > MergeProcessorImpl.doOrderContained() shows the following for source and result ModelAnnotationImpl. > ProducerName and ProducerVersion are lost. > sourceObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@30298bbf (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: Teiid Designer, ProducerVersion: 8.2.0) > resultObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@d3b11c3 (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: null, ProducerVersion: null) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1706) During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1706?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1706: -------------------------------------- Assignee: Paul Richardson > During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1706 > URL: https://issues.jboss.org/browse/TEIIDDES-1706 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2 > > > MergeProcessorImpl.doOrderContained() shows the following for source and result ModelAnnotationImpl. > ProducerName and ProducerVersion are lost. > sourceObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@30298bbf (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: Teiid Designer, ProducerVersion: 8.2.0) > resultObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@d3b11c3 (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: null, ProducerVersion: null) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1751) Using Database Explorer, requires running server in order to connect using Teiid JDBC driver

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1751?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1751. --------------------------------------- Resolution: Done Fixed in master branch. Teiid Driver is now obtained from the runtime client plugin that matches the version of the Teiid server being connected to. > Using Database Explorer, requires running server in order to connect using Teiid JDBC driver > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1751 > URL: https://issues.jboss.org/browse/TEIIDDES-1751 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 8.2 > > > When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1751) Using Database Explorer, requires running server in order to connect using Teiid JDBC driver

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1751?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1751: ----------------------------------- Summary: Using Database Explorer, requires running server in order to connect using Teiid JDBC driver (was: Using Database Developer, requires running server in order to connect using Teiid JDBC driver) > Using Database Explorer, requires running server in order to connect using Teiid JDBC driver > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1751 > URL: https://issues.jboss.org/browse/TEIIDDES-1751 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 8.2 > > > When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1751) Using Database Developer, requires running server in order to connect using Teiid JDBC driver

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1751?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1751: ----------------------------------- Fix Version/s: 8.2 > Using Database Developer, requires running server in order to connect using Teiid JDBC driver > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1751 > URL: https://issues.jboss.org/browse/TEIIDDES-1751 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 8.2 > > > When using Database Developer, created a new datasource (added Teiid JDBC driver from the file system) to connect to a EAP server running Teiid. I would have expected the connection to Teiid to operate as any other jdbc driver and other SQL tools, but in order to connect, I was required to setup a server in JBDS and start it. Which shouldn't be needed in order to make a jdbc connection to an external database. -- 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, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2013