January 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1664) Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1664?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-1664: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=780691 (was: https://bugzilla.redhat.com/show_bug.cgi?id=780691) > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected BQT results > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-1664 > URL: https://issues.jboss.org/browse/TEIID-1664 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > Attachments: QT_teradata12_Push.vdb > > > Teiid - Teradata queries containing LTRIM and RTRIM on the BQT booleanvalue column are returning unexpected results. The following query should be returning 22 rows but 0 rows are returned. > SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE LTRIM(BQT1.SmallA.BooleanValue) = 'true' ORDER BY intkey > However, if the LTRIM is removed like (SELECT intkey, booleanvalue FROM BQT1.SmallA WHERE BQT1.SmallA.BooleanValue = 'true' ORDER BY intkey) 22 rows are returned. > This should be logged against Teiid 7.4.1 > VDB attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1897) Fix the Teiid Build so that the java docs can be built on the first pass

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1897?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3697 to TEIID-1897: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1897 (was: SOA-3697) Affects Version/s: 7.6.1 (was: 5.3.0 GA) Component/s: Build/Kits (was: EDS) Security: (was: Public) Fix Version/s: 7.6.1 (was: 5.3.0 GA) > Fix the Teiid Build so that the java docs can be built on the first pass > ------------------------------------------------------------------------ > > Key: TEIID-1897 > URL: https://issues.jboss.org/browse/TEIID-1897 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 7.6.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.6.1 > > > In order to build the javadocs in the Teiid project, 2 maven build passes are required to be run. This is because of the order of maven dependencies, causing the javadoc's to fail because the jar's have not been built. A suggested fix is to move the javadocs build into its own project, similarly to how modeshape resolved this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1544) Add a limit to the number of dependent queries that can be issued.

by Steven Hawkins (JIRA)

Add a limit to the number of dependent queries that can be issued. ------------------------------------------------------------------ Key: TEIID-1544 URL: https://issues.jboss.org/browse/TEIID-1544 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 There should be a mechanism to limit the number of dependent join queries generated. Ideally this should apply to both cost and hint based dependent joins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1876) Netezza translator using INTNNOT when it should use INT4NOT

by Paul Nittel (Created) (JIRA)

Netezza translator using INTNNOT when it should use INT4NOT ----------------------------------------------------------- Key: TEIID-1876 URL: https://issues.jboss.org/browse/TEIID-1876 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins This was found during query testing. The query in question is RDBMS_Test_Queries_5700_TestQuery153. With Netezza as the source, this query: SELECT IntKey, BITNOT(IntKey) as BitPart FROM BQT1.SmallA ORDER BY IntKey Produces: Caught SQLException: Error Code:1100 Message:Remote org.teiid.core.TeiidProcessingException: Error Code:1100 Message:Source: Error Code:1100 Message:'ERROR: Function 'INTNNOT(INT4)' does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts ' error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."INTKEY" AS c_0, intNnot(g_0."INTKEY") AS c_1 FROM "SMALLA" AS g_0 ORDER BY c_0] Dev responded with: [It appears] this should be calling INT4NOT. The Netezza users guide is a little unclear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
3
0 / 0

[JBoss JIRA] (TEIID-1863) Default Salesforce URL in teiid-connector-salesforce.rar needs update to SF v22

by Mark Drilling (Created) (JIRA)

Default Salesforce URL in teiid-connector-salesforce.rar needs update to SF v22 ------------------------------------------------------------------------------- Key: TEIID-1863 URL: https://issues.jboss.org/browse/TEIID-1863 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Steven Hawkins The salesforce jars were updated using v22 of the salesforce WSDL, however the default URL in teiid-connector.salesforce.rar was not updated. The URL config-property in ra.xml should be changed to: <config-property-value>https://www.salesforce.com/services/Soap/u/22.0</config-property-value> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
3
0 / 0

[JBoss JIRA] (TEIID-1892) Support the get/setArray methods of JDBC resultsets/statements

by Mark Addleman (Created) (JIRA)

Support the get/setArray methods of JDBC resultsets/statements -------------------------------------------------------------- Key: TEIID-1892 URL: https://issues.jboss.org/browse/TEIID-1892 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins We'd like the array related JDBC methods supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

5
6
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-965: -------------------------------------- Ripan non-quoted SQL identifiers are not allowed to have ":", so you need to issue your query with the table name quoted: select * from ExcelData."c:/abcd.Sheet1$" Which if you issue it from the sample command line client will need likely need to be escaped: "select * from ExcelData.\"c:/abcd.Sheet1$\"" Since this is the reported table name (presumably from the TABLES system table), this should work as expected with your JDBC-ODBC source. As Ramesh indicates, getTextFiles is a procedure for file sources (using the file translator with a file datasource) and is not applicable for a JDBC source unless there is a corresponding stored procedure. > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1622) Optional JOIN hints don't get optimized out for UNION ALL view

by Mark Drilling (JIRA)

Optional JOIN hints don't get optimized out for UNION ALL view -------------------------------------------------------------- Key: TEIID-1622 URL: https://issues.jboss.org/browse/TEIID-1622 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Reporter: Mark Drilling Assignee: Steven Hawkins Fix For: 7.1.1 When we create a view with Optional JOIN hint on it, and execute a query against this view, the hint is properly honored. But if we create a view with UNION ALL on two such views and query the UNION ALL view the optional hint is not honored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1656) Add pushdown support for Searched CASE expression over a UNION

by Mark Drilling (JIRA)

Add pushdown support for Searched CASE expression over a UNION -------------------------------------------------------------- Key: TEIID-1656 URL: https://issues.jboss.org/browse/TEIID-1656 Project: Teiid Issue Type: Enhancement Components: Query Engine, Server Affects Versions: 7.4, 7.1.1 Reporter: Mark Drilling Assignee: Steven Hawkins Fix For: 7.4.1 1) User has created a view MyView containing UNION all of two other views, eg "SELECT * FROM View1 UNION ALL SELECT * FROM View 2". 2) Then a user query containing a searched CASE type expression is submitted against the view, eg "SELECT CASE WHEN StringNum IS NULL THEN 0 ELSE 1 END FROM MyView" 3) With current planner the CASE expression is not pushed down to the individual sources. The enhancement request is to allow the pushdown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1623) ODBC numeric and string precision issues

by Mark Drilling (JIRA)

ODBC numeric and string precision issues ---------------------------------------- Key: TEIID-1623 URL: https://issues.jboss.org/browse/TEIID-1623 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.4, 7.3, 7.2, 7.1.1, 7.1 Reporter: Mark Drilling Assignee: Ramesh Reddy Fix For: 7.4.1, 7.1.1 ODBC is not correctly providing the precision and scale data for any numeric types. String types are also being reported 4 characters less then what is in the metadata. Attaching patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2012