January 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-862) Teiid engine needs to be exposed as a JCA Connector

by Ramesh Reddy (JIRA)

Teiid engine needs to be exposed as a JCA Connector --------------------------------------------------- Key: TEIID-862 URL: https://jira.jboss.org/jira/browse/TEIID-862 Project: Teiid Issue Type: Sub-task Components: Embedded, Server Affects Versions: 6.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.3 DQPCore, which is the main interface for the Teiid engine must be available as a JCA source that is capable of engaging multiple other JCA sources in a data integration solution. This should leverage the "Work Manager" for carrying out any tasks. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-918) Change all package names to org.teiid

by Steven Hawkins (JIRA)

Change all package names to org.teiid ------------------------------------- Key: TEIID-918 URL: https://jira.jboss.org/jira/browse/TEIID-918 Project: Teiid Issue Type: Quality Risk Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 With a major version switch we should change our packages over to teiid. This will need to be coordinated with the designer as well. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-891) Add JDBC import logic to correct unsigned types

by Steven Hawkins (JIRA)

Add JDBC import logic to correct unsigned types ----------------------------------------------- Key: TEIID-891 URL: https://jira.jboss.org/jira/browse/TEIID-891 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.0 SQLServer/MySQL and other dbs have support for unsigned types. We should be able to import these types as a wider type to ensure that we can access the values. -- 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

14 years, 6 months

2
2
0 / 0

[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

14 years, 6 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

14 years, 6 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

14 years, 6 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

14 years, 6 months

2
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

14 years, 6 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

14 years, 6 months

3
5
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

14 years, 6 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2010