March 2013 - teiid-designer-issues

[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 moved TEIID-2431 to TEIIDDES-1618: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1618 (was: TEIID-2431) Affects Version/s: (was: 7.7.4) Component/s: (was: Query Engine) > Support partition statistics > ---------------------------- > > Key: TEIIDDES-1618 > URL: https://issues.jboss.org/browse/TEIIDDES-1618 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > > 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-472) Support multi-source bindings

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDDES-472: --------------------------------------- There is little more to it than above, additional properties and source names. see https://docs.jboss.org/author/display/TEIID/Multi-Source+Models > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-472) Support multi-source bindings

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Barry LaFond edited comment on TEIIDDES-472 at 3/11/13 3:50 PM: ---------------------------------------------------------------- Teiid VDB documentation states: *Source Element* A source is a named binding of a translator and connection source to a model. * name ** The name of the source to use for this model. This can be any name you like, but will typically be the same as the model name. Having a name different than the model name is only useful in multi-source scenarios. In multi-source, the source names under a given model must be unique. If you have the same source bound to multiple models it may have the same name for each. An exception will be raised if the same source name is used for different sources. * translator-name ** The name or type of the Teiid Translator to use. Possible values include the built-in types (ws, file, ldap, oracle, sqlserver, db2, derby, etc.) and translators defined in the translators section. * connection-jndi-name ** The JNDI name of this source's connection factory. There should be a corresponding "-ds.xml" file that defines the connection factory in the JBoss AS. Check out the deploying VDB dependencies section for info. You also need to deploy these connection factories before you can deploy the VDB. So a multi-source binding elements could look something like the following ? <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts_SQLSERVER" name="Customer_Accounts_1"/> <source translator-name="mysql" connection-jndi-name="Customer_Accounts_MYSQL" name="Customer_Accounts_2"/> <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts_SQL_SERVER" name="Customer_Accounts_3"/> was (Author: blafond): Teiid VDB documentation states: *Source Element* A source is a named binding of a translator and connection source to a model. * name ** The name of the source to use for this model. This can be any name you like, but will typically be the same as the model name. Having a name different than the model name is only useful in multi-source scenarios. In multi-source, the source names under a given model must be unique. If you have the same source bound to multiple models it may have the same name for each. An exception will be raised if the same source name is used for different sources. * translator-name ** The name or type of the Teiid Translator to use. Possible values include the built-in types (ws, file, ldap, oracle, sqlserver, db2, derby, etc.) and translators defined in the translators section. * connection-jndi-name ** The JNDI name of this source's connection factory. There should be a corresponding "-ds.xml" file that defines the connection factory in the JBoss AS. Check out the deploying VDB dependencies section for info. You also need to deploy these connection factories before you can deploy the VDB. So a multi-source binding elements would look something like the following ? <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_1"/> <source translator-name="mysql" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_2"/> <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_3"/> > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-472) Support multi-source bindings

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-472: --------------------------------------- Teiid VDB documentation states: *Source Element* A source is a named binding of a translator and connection source to a model. * name ** The name of the source to use for this model. This can be any name you like, but will typically be the same as the model name. Having a name different than the model name is only useful in multi-source scenarios. In multi-source, the source names under a given model must be unique. If you have the same source bound to multiple models it may have the same name for each. An exception will be raised if the same source name is used for different sources. * translator-name ** The name or type of the Teiid Translator to use. Possible values include the built-in types (ws, file, ldap, oracle, sqlserver, db2, derby, etc.) and translators defined in the translators section. * connection-jndi-name ** The JNDI name of this source's connection factory. There should be a corresponding "-ds.xml" file that defines the connection factory in the JBoss AS. Check out the deploying VDB dependencies section for info. You also need to deploy these connection factories before you can deploy the VDB. So a multi-source binding elements would look something like the following ? <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_1"/> <source translator-name="mysql" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_2"/> <source translator-name="sqlserver" connection-jndi-name="Customer_Accounts" name="Customer_Accounts_3"/> > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-472) Support multi-source bindings

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIIDDES-472: --------------------------------------- We need UI work in the VDB explorer where a model can be defined as multi-source, and able to assign multiple sources to it. > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-472) Support multi-source bindings

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-472: ------------------------------------- Assignee: Barry LaFond > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Assignee: Barry LaFond > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-472) Support multi-source bindings

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-472: ---------------------------------- Fix Version/s: 8.1 (was: Future) > Support multi-source bindings > ----------------------------- > > Key: TEIIDDES-472 > URL: https://issues.jboss.org/browse/TEIIDDES-472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.3 > Reporter: John Verhaeg > Fix For: 8.1 > > > Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. > The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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-1616) Add Header Support to Generated REST WAR

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1616?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1616: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=920287 > Add Header Support to Generated REST WAR > ---------------------------------------- > > Key: TEIIDDES-1616 > URL: https://issues.jboss.org/browse/TEIIDDES-1616 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.8 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.7.2, 8.1 > > > Need to add support for using headers in the generated REST WAR. The headers will be used as parameters to the target procedure for an operation. -- 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-1617) Capture view definition from database and apply as transformation query for viewModel table

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-1617: -------------------------------------- Summary: Capture view definition from database and apply as transformation query for viewModel table Key: TEIIDDES-1617 URL: https://issues.jboss.org/browse/TEIIDDES-1617 Project: Teiid Designer Issue Type: Feature Request Reporter: Tom Johnston -- 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-1616) Add Header Support to Generated REST WAR

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1616: ----------------------------------- Summary: Add Header Support to Generated REST WAR Key: TEIIDDES-1616 URL: https://issues.jboss.org/browse/TEIIDDES-1616 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Affects Versions: 7.8 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.7.2, 8.1 Need to add support for using headers in the generated REST WAR. The headers will be used as parameters to the target procedure for an operation. -- 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