April 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1990) UNION pushdown

by Mark Addleman (JIRA)

Mark Addleman created TEIID-1990: ------------------------------------ Summary: UNION pushdown Key: TEIID-1990 URL: https://issues.jboss.org/browse/TEIID-1990 Project: Teiid Issue Type: Bug Reporter: Mark Addleman Assignee: Steven Hawkins I have SQL of the form SELECT a FROM ( SELECT a FROM ds.t1 UNION SELECT a FROM ds.t2 ) t The execution factory extends JDBCExecutionFactory and supports everything except row offset. It appears that the two unioned SELECTs are being executed as separate statements rather than the entire unioned set being pushed down to the datasource. Attached is plan -- 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

11 years, 9 months

2
13
0 / 0

[JBoss JIRA] (TEIID-1962) EDS Ingres10 as Source - LOCATE function not returning correct query results

by Warren Gibson (JIRA)

Warren Gibson created TEIID-1962: ------------------------------------ Summary: EDS Ingres10 as Source - LOCATE function not returning correct query results Key: TEIID-1962 URL: https://issues.jboss.org/browse/TEIID-1962 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Warren Gibson Assignee: Steven Hawkins EDS query testing using Ingres 10 as the source is returning unexpected query results for 4 queries involving LOCATE function. Spreadsheet is attached showing the queries involved and the query results. -- 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

11 years, 9 months

3
13
0 / 0

[JBoss JIRA] (TEIID-1871) Teiid is handling MySQL5.0 returning DAYNAME as a blob

by Paul Nittel (Created) (JIRA)

Teiid is handling MySQL5.0 returning DAYNAME as a blob ------------------------------------------------------ Key: TEIID-1871 URL: https://issues.jboss.org/browse/TEIID-1871 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: mysql-connector-java-5.0.8-bin.jar, QT_MySql50_Push-ds.xml, QT_MySql50_Push.vdb SELECT IntKey, DAYNAME(datevalue) FROM BQT1.SmallA ORDER BY IntKey LIMIT 10 Fails with: Caught SQLException: Invalid conversion from type class org.teiid.core.types.BlobType with value 'javax.sql.rowset.serial.SerialBlob@6482112e' to type class java.lang.String Dev indicaters, "The driver returns the bytes, which we treat as a blob. We have an explicit workaround in the translator for the char function, but I've never seen this outside of the char function. There may be an issue with the http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysva... setting also that could influence how the value is returned." The server setting is en_US. -- 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

11 years, 9 months

6
12
0 / 0

[JBoss JIRA] (TEIID-1981) Admin API does not correctly in Domain mode

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1981: ----------------------------------- Summary: Admin API does not correctly in Domain mode Key: TEIID-1981 URL: https://issues.jboss.org/browse/TEIID-1981 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 Lot of Admin API methods does not seem work with Domain mode of operation. This is true for CLI based operations on Teiid too. -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1987) Exception Processing Web Service Response

by Ted Jones (JIRA)

Ted Jones created TEIID-1987: -------------------------------- Summary: Exception Processing Web Service Response Key: TEIID-1987 URL: https://issues.jboss.org/browse/TEIID-1987 Project: Teiid Issue Type: Bug Components: XML Planner/Processor Affects Versions: 7.7 Reporter: Ted Jones Assignee: Steven Hawkins After modeling a web service operation using the Web Service to Source Importer, I previewed the wrapper procedure from Designer and encountered the following error in Teiid: 14:26:03,175 INFO [ReflectionServiceFactoryBean] Creating Service {http://teiid.org}teiid from class org.apache.cxf.jaxws.support.DummyImpl 14:26:03,177 INFO [ConfigurerImpl] Could not determine bean name for instance of class org.apache.cxf.jaxws.DispatchImpl. 14:26:05,681 WARN [PROCESSOR] Processing exception 'Error building Source for context item.' for request 8GKEIB7qIorN.0. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.query.processor.relational.XMLTableNode.processRow(XMLTableNode.java:287). Enable more detailed logging to see the entire stacktrace. The web service WSDL is: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL The operation modelled and executed was "FullCountryInfoAllCountries" -- 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

11 years, 9 months

3
6
0 / 0

[JBoss JIRA] (TEIID-1840) The Jdbc Socket Host Name Propertie cannot be changed in admin console

by Nagai Eiichi (Created) (JIRA)

The Jdbc Socket Host Name Propertie cannot be changed in admin console ---------------------------------------------------------------------- Key: TEIID-1840 URL: https://issues.jboss.org/browse/TEIID-1840 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.4 Reporter: Nagai Eiichi Assignee: Steven Hawkins The Jdbc Socket Host Name property cannot be changed in admin console. -- 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

11 years, 9 months

6
6
0 / 0

[JBoss JIRA] (TEIID-2004) Support 1.7 JDBC methods

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2004: ------------------------------------- Summary: Support 1.7 JDBC methods Key: TEIID-2004 URL: https://issues.jboss.org/browse/TEIID-2004 Project: Teiid Issue Type: Task Components: JDBC Driver Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 To build against a 1.7 VM without retarging to a 1.6 runtime for the Java libraries requires that we update our JDBC logic to add missing methods. Most will likely still not be supported and will throw a SQLFeatureUnsupported exception where appropriate. -- 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

11 years, 9 months

3
19
0 / 0

[JBoss JIRA] (TEIID-1951) CommandLogging is refers to the old MMx connectorBindingName, when it should refer to it a translator

by Van Halbert (JIRA)

Van Halbert created TEIID-1951: ---------------------------------- Summary: CommandLogging is refers to the old MMx connectorBindingName, when it should refer to it a translator Key: TEIID-1951 URL: https://issues.jboss.org/browse/TEIID-1951 Project: Teiid Issue Type: Bug Components: Documentation, Server Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor In the command logging, the translator is still be referred to as the connectorBindingName: 2012-02-22 16:01:53,712 DEBUG [org.teiid.COMMAND_LOG] (Worker1_QueryProcessorQueue11 START DATA SRC COMMAND: startTime=2012-02-22 16:01:53.712 requestID=Ku4/dgtZPYk0.5 sourceCommandID=4 txID=null modelName=DTHCP connectorBindingName=jdbc-simple sessionID=Ku4/dgtZPYk0 principal=user@teiid-security sql=HCP_ADDR_XREF.HUB_ADDR_ID, CPN_PROMO_HIST.PROMO_STAT_DT FROM CPN_PROMO_HIST, HCP_ADDRESS, HCP_ADDR_XREF WHERE (HCP_ADDRESS.ADDR_ID = CPN_PROMO_HIST.SENT_ADDR_ID) AND (HCP_ADDRESS.ADDR_ID = HCP_ADDR_XREF.ADDR_ID) AND (CPN_PROMO_HIST.PROMO_STAT_CD NOT LIKE 'EMAIL%') AND (CPN_PROMO_HIST.PROMO_STAT_CD <> 'SENT_EM') AND (CPN_PROMO_HIST.PROMO_STAT_DT > {ts'2010-02-22 16:01:52.928'}) Also, it would be good to include an example of this output in the documentation of what will be seen. -- 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

11 years, 9 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1911) Deploy time cached VDB metadata is being deleted during shutdown.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1911: ----------------------------------- Summary: Deploy time cached VDB metadata is being deleted during shutdown. Key: TEIID-1911 URL: https://issues.jboss.org/browse/TEIID-1911 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 8.0 Due to https://issues.jboss.org/browse/AS7-3431 the metadata is always being deleted during the shutdown. This will be bigger issue with dynamic VDBs. -- 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

11 years, 9 months

2
6
0 / 0

[JBoss JIRA] (TEIID-1964) Queries which exceed the query timeout value are reported as canceled with no reference to the reason (timed out)

by Paul Nittel (JIRA)

Paul Nittel created TEIID-1964: ---------------------------------- Summary: Queries which exceed the query timeout value are reported as canceled with no reference to the reason (timed out) Key: TEIID-1964 URL: https://issues.jboss.org/browse/TEIID-1964 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: TimedOut.log While testing the query timeout value setting for VDBs in the Designer, I found there was no way for a user to easily understand why requests were being canceled due to a timeout. The log shows nothing other than it was canceled. The phrase timeout did not appear in the log. We really should report the cause of the cancellation. I'll attach the log excerpt. -- 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

11 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2012