March 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-803) The connector binding name assigned when created in the designer is not the name in the ConnectorBinding when using AdminAPI

by Van Halbert (JIRA)

The connector binding name assigned when created in the designer is not the name in the ConnectorBinding when using AdminAPI ---------------------------------------------------------------------------------------------------------------------------- Key: TEIID-803 URL: https://jira.jboss.org/jira/browse/TEIID-803 Project: Teiid Issue Type: Bug Components: AdminApi, Tools Affects Versions: 6.2.0 Reporter: Van Halbert Assignee: Steven Hawkins The name I assigned to the connectorbinding in the designer was "datasource1". I looked at the advanced properties and there is no other name property defined. Open the vdb file and view the Configuration.def file and it has the following: <Connector Name="datasource1" ComponentType="Loopback Connector" routingUUID="mmuuid:66dfa66b-4572-46ba-a477-8b6fe3895072"> <Properties> <Property Name="DeployedName">Transaction_1.datasource1</Property> </Properties> </Connector> When using the adminapi and calleding getName() on ConnectorBinding, the name returned is "Transaction_1.datasource1". The name that the user assignes to the binding should match the getName(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-924) Remove metadataobjects

by Steven Hawkins (JIRA)

Remove metadataobjects ---------------------- Key: TEIID-924 URL: https://jira.jboss.org/jira/browse/TEIID-924 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 As long as we can rely on the querymetadatainterface being backed by our impls, then the use of the connector api metadataobjects becomes unnecessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-927) Remove the legacy JDBC Datasource and Driver classes

by Ramesh Reddy (JIRA)

Remove the legacy JDBC Datasource and Driver classes ---------------------------------------------------- Key: TEIID-927 URL: https://jira.jboss.org/jira/browse/TEIID-927 Project: Teiid Issue Type: Task Components: JDBC Driver Reporter: Ramesh Reddy Fix For: 7.0 Delete EmbeddedDataSource EmbeddedDriver MMDriver MMDataSource classes from the JDBC library as Teiid already provides a replacement driver and data source since 6.2 release The replacement classes are TeiidDriver TeiidDataSource these will handle both server and embedded connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-915) Error results in illegalstateexception

by Steven Hawkins (JIRA)

Error results in illegalstateexception -------------------------------------- Key: TEIID-915 URL: https://jira.jboss.org/jira/browse/TEIID-915 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 If results have already been sent and an exception occurs prior to the next batch request the result is an illegalstateexception. It would be better to just log that we aren't sending the exception to the client. Note that this only affects multi-batch non-transactional execution. In general there's no good way to ensure that the client will see the exception, since they aren't required to use the entire result set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1023) Chanage "MaxResultRows" Connector Property to default to "unlimited"

by Ramesh Reddy (JIRA)

Chanage "MaxResultRows" Connector Property to default to "unlimited" -------------------------------------------------------------------- Key: TEIID-1023 URL: https://jira.jboss.org/jira/browse/TEIID-1023 Project: Teiid Issue Type: Task Components: Connector API Reporter: Ramesh Reddy Fix For: 7.0 Teiid supports a property called "MaxResultRows" in Connector properties, which defaults to 10,000 rows. The expected behavior of this is to throw an exception when user queries more than 10,000 rows through this connector. However, this default behavior seems like a exceptional condition than normal behavior expected by user any time. This *was* designed more for the development time aid than the runtime. Here is an example of community user tripping over it. http://community.jboss.org/message/532560#532560 I propose, we change the default value of this property to "-1" that means the "MaxResultRows" will be set to "unlimited" in the default scenario. If user requires to restrict max rows they can *explicitly* set a value that they are comfortable with. Note the default "unlimited" is value changed from "0" to "-1". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-939) MySQL nested set query pushdown failure

by Steven Hawkins (JIRA)

MySQL nested set query pushdown failure --------------------------------------- Key: TEIID-939 URL: https://jira.jboss.org/jira/browse/TEIID-939 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 By default our translator is adding parens around nested set queries, this is not supported by MySQL. The parens can safely be dropped as long as both the parent and the child are the same set operation (union, or union all). The only problem for MySQL is that you cannot left nest a union all under a union. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-781) Move the CTC testing framework to the teiid community

by Van Halbert (JIRA)

Move the CTC testing framework to the teiid community ----------------------------------------------------- Key: TEIID-781 URL: https://jira.jboss.org/jira/browse/TEIID-781 Project: Teiid Issue Type: Sub-task Reporter: Van Halbert Fix For: 6.2.0 The CTC testing client used by QE for testing MetaMatrix and Teiid needs to be moved to the teiid community. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-948) Spurious wake-up error with connector work item

by Steven Hawkins (JIRA)

Spurious wake-up error with connector work item ----------------------------------------------- Key: TEIID-948 URL: https://jira.jboss.org/jira/browse/TEIID-948 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 If a synch work items has a spurious wake up, that can cause state exceptions in start/end processing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-926) Reduce use of map look ups for projection

by Steven Hawkins (JIRA)

Reduce use of map look ups for projection ----------------------------------------- Key: TEIID-926 URL: https://jira.jboss.org/jira/browse/TEIID-926 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.0 GroupingNode, SelectNode, and JoinNode are using map lookups to project tuples. This should be precomputed instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-898) Named procedure parameter error message too terse.

by Steven Hawkins (JIRA)

Named procedure parameter error message too terse. -------------------------------------------------- Key: TEIID-898 URL: https://jira.jboss.org/jira/browse/TEIID-898 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 7.0 The error message for a named procedure "EXEC VirtProcs.dyno( virtprocs.dyno.timein='04:00:00', virtprocs.dyno.byteme=125)" error is Invalid param name(s): [VIRTPROCS.DYNO.BYTEME, VIRTPROCS.DYNO.TIMEIN] which doesn't give any indication as to what names are expected, it just returns the names used in upper case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2010