March 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1620) Add Multi-source bindings editing feature to VDB Editor

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1620: -------------------------------------- Summary: Add Multi-source bindings editing feature to VDB Editor Key: TEIIDDES-1620 URL: https://issues.jboss.org/browse/TEIIDDES-1620 Project: Teiid Designer Issue Type: Sub-task Components: Editors, VDB & Execution Affects Versions: 8.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 8.1 Current VDB Editor is designed to manage a single source definition (name, jndi-name and translator-name) for each source model. The UI/Editor needs to allow for defining multiple "sources" for a each source 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1619) Add VdbSources and VdbSource objects to replace single source name, jndi-name and translator-name in VdbModelEntry

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1619: -------------------------------------- Summary: Add VdbSources and VdbSource objects to replace single source name, jndi-name and translator-name in VdbModelEntry Key: TEIIDDES-1619 URL: https://issues.jboss.org/browse/TEIIDDES-1619 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution Affects Versions: 8.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 8.1 VdbModelEntry class manages a single source via local name, jndi-name and translator-name class variables. This needs to move to a VdbSources multi-source object that holds VdbSource object Map that contains these same 3 properties. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1618) Support partition statistics

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1618: --------------------------------------- I think the implementation to this could require a lot of work. Example, for each data source that is partitioned, the following information would possibly need to be tracked: - for each partition, what is the algorithm - depending on the algorithm, what columns and what criteria used - in designer, at import time, would need ask user if its partitioned and would need to know how to issue database specific commands to get stats per partition, and then store in the model. - server stat refresh would need to be able to refresh based on partition And the logic changes (I'm assuming here) related to cardinality optimization depending upon the criteria on the incoming query and using the corresponding cardinality according to how its partitioned. I think this request is doable, but will take some time to work out all the details. > Support partition statistics > ---------------------------- > > Key: TEIIDDES-1618 > URL: https://issues.jboss.org/browse/TEIIDDES-1618 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Van Halbert > > The stats gathering feature does not take into account of partition statistics. Most of our query hit a single partition and using the global stats is not a true indication of the statistics for the single partition. It would be nice if Teiid engine can differentiate the usage of global and partition statistics during the optimisation and planning stages. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1618) Support partition statistics

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1618?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1618: ------------------------------------------ There are multiple considerations here. The first is that if its true that most (if not all queries) hit a single partition, then there could be an option to pull representative statistics for just a single partition (which would require a change to the stats gathering). If that's still not representative, and the source partitions can be directly referenced and list partitioning is used then the source table could be represented as a partitioned view with each partition having it's individual statistics (which may require a change to the stats gathering) - this could be a designer assisted option. And or, with additional metadata, such as specifying the partitioning value lists via a metadata extension (which would be needed in the relational metamodel) and provide the individual stats via an extension as well, then Teiid could internally handle the more appropriate costing based upon the metadata. If range or other partitioning is in use then that would require additional work for Teiid to recognize additional partitioning schemes. So more input would be helpful from the owner as to the details of the partitioning scheme, etc. to determine the appropriate actions. > Support partition statistics > ---------------------------- > > Key: TEIIDDES-1618 > URL: https://issues.jboss.org/browse/TEIIDDES-1618 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Van Halbert > > The stats gathering feature does not take into account of partition statistics. Most of our query hit a single partition and using the global stats is not a true indication of the statistics for the single partition. It would be nice if Teiid engine can differentiate the usage of global and partition statistics during the optimisation and planning stages. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1482) Going from SVN to git rendered "Setting Up Your Teiid Designer Eclipse Environment" obsolete-ish

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1482?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1482. ------------------------------------ Assignee: Barry LaFond Fix Version/s: 8.1 Resolution: Out of Date Replaced Wiki page with instructions with GIT repo for 8.x Designer codebase > Going from SVN to git rendered "Setting Up Your Teiid Designer Eclipse Environment" obsolete-ish > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1482 > URL: https://issues.jboss.org/browse/TEIIDDES-1482 > Project: Teiid Designer > Issue Type: Task > Components: Documentation > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > > The doc, located at https://community.jboss.org/wiki/SettingUpYourTeiidDesignerEclipseEnviron... refers to the older svn repository and needs to be updated to include git instead. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1575: ----------------------------------- Description: Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. Potential DBs include: * Hive - TEIIDDES-1193 * Mondrian - TEIIDDES-930 * Intersystems Cache - TEIIDDES-904 * Ingres - TEIIDDES-883 * LDAP - TEIIDDES-305 * Greenplum - TEIIDDES-1593 was: Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. Potential DBs include: * Hive - TEIIDDES-1193 * Mondrian - TEIIDDES-930 * Intersystems Cache - TEIIDDES-904 * Ingres - TEIIDDES-883 * LDAP - TEIIDDES-305 > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 > * Greenplum - TEIIDDES-1593 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1575: ----------------------------------- Description: Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. Potential DBs include: * Hive - TEIIDDES-1193 * Mondrian - TEIIDDES-930 * Intersystems Cache - TEIIDDES-904 * Ingres - TEIIDDES-883 * LDAP - TEIIDDES-305 * Greenplum - TEIIDDES-1557 was: Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. Potential DBs include: * Hive - TEIIDDES-1193 * Mondrian - TEIIDDES-930 * Intersystems Cache - TEIIDDES-904 * Ingres - TEIIDDES-883 * LDAP - TEIIDDES-305 * Greenplum - TEIIDDES-1593 > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 > * Greenplum - TEIIDDES-1557 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1549: ---------------------------------------- I believe this bug was fixed with TEIIDDES-1614 fix? > Web service (and possibly other) procedures fail validation > ----------------------------------------------------------- > > Key: TEIIDDES-1549 > URL: https://issues.jboss.org/browse/TEIIDDES-1549 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: PartsBeforeLunch_MPS.zip > > > Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set. > There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command. > The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1549: ----------------------------------- Assignee: Paul Richardson > Web service (and possibly other) procedures fail validation > ----------------------------------------------------------- > > Key: TEIIDDES-1549 > URL: https://issues.jboss.org/browse/TEIIDDES-1549 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: PartsBeforeLunch_MPS.zip > > > Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set. > There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command. > The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1549: ----------------------------------- Fix Version/s: 8.1 > Web service (and possibly other) procedures fail validation > ----------------------------------------------------------- > > Key: TEIIDDES-1549 > URL: https://issues.jboss.org/browse/TEIIDDES-1549 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.0 > Reporter: Steven Hawkins > Fix For: 8.1 > > Attachments: PartsBeforeLunch_MPS.zip > > > Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set. > There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command. > The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result. -- 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

13 years, 1 month

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 March 2013