June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1074) Make VDB work with Model based index files

by Ramesh Reddy (JIRA)

Make VDB work with Model based index files ------------------------------------------ Key: TEIID-1074 URL: https://jira.jboss.org/jira/browse/TEIID-1074 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 7.0 Reporter: Ramesh Reddy Priority: Blocker Fix For: 7.0 Currently the VDB generated from the Designer, generates the metadata in the form of Index file that are type based. i.e. there is index file for tables, columns, procedures etc. This is done before for speed of access from the index file to retrieve the metadata. Going forward, Designer team is looking into providing the same metadata in the form of "Model" index files. This means all the metadata for the model is placed in a single index file, so if there are multiple models, then table, column information from two different tables in two different models are spread across two files. Teiid runtime should be modified such that this form of index files can be read. The issue of speed to not existent, because Teiid upon reading it, converts the Metadata Store format and keeps a object form of it locally in the memory and on the disk. The sample VDB is attached. Fix the vdb.xml file before start. -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIID-1024) Support conversion between clob and sql/xml

by Steven Hawkins (JIRA)

Support conversion between clob and sql/xml ------------------------------------------- Key: TEIID-1024 URL: https://jira.jboss.org/jira/browse/TEIID-1024 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins We should support the conversion between sql/xml and clob to broaden the ability of users to treat values as xml. -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-906) Add support for a set statement

by Steven Hawkins (JIRA)

Add support for a set statement ------------------------------- Key: TEIID-906 URL: https://jira.jboss.org/jira/browse/TEIID-906 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 We should add support in the JDBC driver to set execution properties via a set statement. This makes it unnecessary to us the custom MMStatement api in most circumstances. -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIID-833) Support tighter integration with container deployments

by Steven Hawkins (JIRA)

Support tighter integration with container deployments ------------------------------------------------------ Key: TEIID-833 URL: https://jira.jboss.org/jira/browse/TEIID-833 Project: Teiid Issue Type: Feature Request Components: Embedded, Query Engine, Server Affects Versions: 6.3.0 Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 6.3.0 We should be able to leverage the container: TransactionManager/XATerminator Work Management Security Connection Handling (See also TEIID-805) and have a standard deployment model for JON discovery. The initial plans are to deploy Teiid as a JCA rar and to allow for the creation of local (embedded) datasources from that instance, as well as allow for socket 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

4
4
0 / 0

[JBoss JIRA] Updated: (TEIID-177) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-177?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-177: -------------------------------- Affects Version/s: 6.0.0 (was: 8.x) 1.5 support is relatively easy to achieve with retrotranslator, but there are some issues. We need to add backports of NClob, Wrapper, and SQLXML. There is also a non-public method that needs exposed on ObjectStreamClass. The worst thing though is that PlanNode depends upon JAXB, which is not in older JREs by default. We would either need to provide a JAXB free backport, or require that the customer installs JAXB. With those changes though I was able to successfully query a 7.0 server using a 1.5 JRE client. Moving back to 1.4 would then not be that difficult, but would require a couple of changes to add support for a few missing JRE methods. > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-177 > URL: https://jira.jboss.org/browse/TEIID-177 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 7.1 > > > The jdbc driver needs to support jdk 1.5 on the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1001) Source string format for float/double/bigdecimal/timestamp can vary

by Steven Hawkins (JIRA)

Source string format for float/double/bigdecimal/timestamp can vary ------------------------------------------------------------------- Key: TEIID-1001 URL: https://jira.jboss.org/jira/browse/TEIID-1001 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Teiid uses JDBC/Java for it's standard conversions. However the push down conversion to string of float/double/bigdecimal/timestamp can vary depending upon the actual source type and source system (db2 vs. sql server, etc.). -- 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] Closed: (TEIID-165) Connector support for more converts

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-165?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-165. ------------------------------- > Connector support for more converts > ----------------------------------- > > Key: TEIID-165 > URL: https://jira.jboss.org/browse/TEIID-165 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.0 > > > Defect Tracker #24822: Connector support for more converts (from object, clob, xml). Query changes are needed to remove the check from CapabilitiesUtil that is preventing the push down. Additionally defect 15144 should be worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-782) Add the ability to test transactions to CTC testing client

by Van Halbert (JIRA)

Add the ability to test transactions to CTC testing client ---------------------------------------------------------- Key: TEIID-782 URL: https://jira.jboss.org/jira/browse/TEIID-782 Project: Teiid Issue Type: Sub-task Reporter: Van Halbert Fix For: 6.2.0 The CTC Client needs the ability to test transactions. The idea here was to change the framework to use the transaction framework used in the jbedsp-test-integration tests. -- 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] Closed: (TEIID-856) CTC Query Results have special characters in some cases depending on the OS causing unexpected results

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-856?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-856. ------------------------------- > CTC Query Results have special characters in some cases depending on the OS causing unexpected results > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-856 > URL: https://jira.jboss.org/browse/TEIID-856 > Project: Teiid > Issue Type: Bug > Components: Integration Tests > Affects Versions: 7.0 > Reporter: Warren Gibson > Assignee: Van Halbert > > In some cases query error results are being returned to CTC with special characters depending on the OS. This results in unexpected results since CTC use the same set of expected results for all OS versions. Please strip off special characters from query results in CTC to accommodate differences between OS behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-188) Improve resolution of parameter references used in compare criteria

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-188?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-188. ------------------------------- > Improve resolution of parameter references used in compare criteria > ------------------------------------------------------------------- > > Key: TEIID-188 > URL: https://jira.jboss.org/browse/TEIID-188 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Mark Drilling > Assignee: Steven Hawkins > Priority: Minor > Attachments: GregComments.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Entering this JIRA from Issue 185605 in issue tracker. Greg Haber reports problem using Penrose off the shelf application. Example query as follows > select distinct petOwnersFromMM.owner, petOwnersFromMM.name from petVirtualDB.gregtest_virtual.gregtest.pet petOwnersFromMM where lower(petOwnersFromMM.owner) = lower(?) order by petOwnersFromMM.owner > He is getting "com.metamatrix.jdbc.MMSQLException: The function 'lower(?)' has more than one possible signature." since the lower function is ambiguous. > Workaround is to use "lower(convert(?, string))" in the sql. There is a statement in the release notes for a future enhancement that we could use the type info from the other side of the compare criteria to determine what the type should be. > I will attach Gregs further comments for reference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 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-issues June 2010