December 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1675) Add capability to insert/update/delete multi-value attributes in LDAP connector

by Marc Shirley (JIRA)

Add capability to insert/update/delete multi-value attributes in LDAP connector ------------------------------------------------------------------------------- Key: TEIID-1675 URL: https://issues.jboss.org/browse/TEIID-1675 Project: Teiid Issue Type: Feature Request Components: LDAP Connector Affects Versions: 7.4 Reporter: Marc Shirley Assignee: Steven Hawkins Add ability to insert/update/delete multi-value attributes through the LDAP connector. For example, this would present the opportunity for maintaining group membership through modifying the list of member attribute values in an LDAP groupOfNames object. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
4
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, 11 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, 11 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, 11 months

4
3
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, 11 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, 11 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1495) Validate the TeraData Translator

by Ramesh Reddy (JIRA)

Validate the TeraData Translator -------------------------------- Key: TEIID-1495 URL: https://issues.jboss.org/browse/TEIID-1495 Project: Teiid Issue Type: Task Components: JDBC Connector Affects Versions: 7.3 Reporter: Ramesh Reddy Fix For: 7.4 Currently the Teiid does provide a Teradata translator, however it has been taken from the old MMX code, however it was never validated with Teiid to make sure this works correctly with the data source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

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

by Ripan Karmakar (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ripan Karmakar commented on TEIID-965: -------------------------------------- I have followed the same process as mentioned by Warren. I could able to make the connection but not able to retrieve data from the excel. I am using the following query to connect to the VDB schema sqlForExcel = "SELECT * FROM ExcelData.('Sheet1$')"; Where ExcelData is my schema name and Sheet1$ is the worksheetname. Can you please tell if I need to change the query > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIID-987) Problem regarding how often availability is called on the Facet

by Ted Jones (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-987?page=com.atlassian.jira.plugin.... ] Ted Jones resolved TEIID-987. ----------------------------- Resolution: Out of Date Closing since Embedded Jopr is not part of AS 7 > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://issues.jboss.org/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 8.0 > > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- 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

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2011