July 2012 - teiid-issues - Jboss List Archives

[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

12 years, 4 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

12 years, 4 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

12 years, 4 months

3
6
0 / 0

[JBoss JIRA] (TEIID-2053) Various metadata issues

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2053: ------------------------------------- Summary: Various metadata issues Key: TEIID-2053 URL: https://issues.jboss.org/browse/TEIID-2053 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 1. The default for a proc/function should be virtual and the keyword foreign should be used to indicate a source function. 2. The parser should validate a source procedure has no procedure body defined 3. The parser should validate a function has no function body defined. 4. FunctionMethod.getFullName should not use category qualification. 5. A DDL defined function should be schema scoped when referenced in the getSupportedFunctions list 6. MetadataFactory should not extend Schema to avoid the merge operation and to not serialize MetadataFactory information with the objects created. 7. Schema should not have visibility metadata - that is held on the ModelMetaData. -- 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
3
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

12 years, 4 months

6
6
0 / 0

[JBoss JIRA] (TEIID-2043) Dedug query plans can be too large

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2043: ------------------------------------- Summary: Dedug query plans can be too large Key: TEIID-2043 URL: https://issues.jboss.org/browse/TEIID-2043 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 As seen in TEIID-2041 debug logs can grow much too large. The two main culprits are full pre-planning of all subqueries and the amount of information shown on each node for each rule. To address the former we should instead only plan project node subqueries after the initial run of RuleAssignOutputElements, since typically not all columns will be used. For the latter we should consider putting a modified marker on a plannode that will get cleared after a toString to truncate the values shown for a node (in some cases we make modifications to objects held on the node, so it's not quite that simple). -- 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
2
0 / 0

[JBoss JIRA] (TEIID-2055) Error during using Teiid Local connections.

by Vineela Gampa (JIRA)

Vineela Gampa created TEIID-2055: ------------------------------------ Summary: Error during using Teiid Local connections. Key: TEIID-2055 URL: https://issues.jboss.org/browse/TEIID-2055 Project: Teiid Issue Type: Bug Environment: windows Reporter: Vineela Gampa Assignee: Steven Hawkins Fix For: 7.7.1 Appplication fails with the below exceptions when using Teiid Local connections.Tried "passthroughAuthentication=true" but it fails during getConnection() our application flow is UI (GWT Layer) -> GWT RPC Services (our service) -> TEIID (translator / database). we are hitting the exception shown above when we launch up our application where GWT is making call to one of the GWT service which internally makes connections to teiid to retrieve the data.. [14:03:37.976][info][talledLocalContainer] 16 May 2012 14:03:37,975 PDT ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing [14:03:37.976][info][talledLocalContainer] java.lang.IllegalStateException: Security Context is null [14:03:37.976][info][talledLocalContainer] at org.jboss.web.tomcat.security.SecurityAssociationActions$PopRunAsRoleAction.run(SecurityAssociationActions.java:156) [14:03:37.976][info][talledLocalContainer] at java.security.AccessController.doPrivileged(Native Method) [14:03:37.976][info][talledLocalContainer] at org.jboss.web.tomcat.security.SecurityAssociationActions.popRunAsIdentity(SecurityAssociationActions.java:302) [14:03:37.976][info][talledLocalContainer] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:193) [14:03:37.976][info][talledLocalContainer] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) [14:03:37.977][info][talledLocalContainer] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) [14:03:37.977][info][talledLocalContainer] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) [14:03:37.977][info][talledLocalContainer] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [14:03:37.977][info][talledLocalContainer] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [14:03:37.977][info][talledLocalContainer] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [14:03:37.977][info][talledLocalContainer] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [14:03:37.977][info][talledLocalContainer] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) [14:03:37.977][info][talledLocalContainer] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) [14:03:37.977][info][talledLocalContainer] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) [14:03:37.977][info][talledLocalContainer] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) [14:03:37.977][info][talledLocalContainer] at java.lang.Thread.run(Thread.java:722) [14:03:51.572][info][talledLocalContainer] 16 May 2012 14:03:51,572 PDT WARNING [BrowserLogger] Client side exception: Uncaught exception [14:03:51.572][info][talledLocalContainer] com.google.gwt.user.client.rpc.InvocationException: from ObjectsService_Proxy.getObjects Unknown.Nm(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.kFh(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.KLh(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.nrg(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.Prg(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.Beg(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.Eeg(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.573][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.573][info][talledLocalContainer] [14:03:51.573][info][talledLocalContainer] [14:03:51.612][info][talledLocalContainer] 16 May 2012 14:03:51,612 PDT WARNING [BrowserLogger] Client side exception: Uncaught exception [14:03:51.612][info][talledLocalContainer] com.google.gwt.user.client.rpc.InvocationException: from ObjectsService_Proxy.getObjects Unknown.Nm(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.kFh(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.KLh(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.nrg(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.Prg(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.Beg(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.Eeg(Unknown Source) [14:03:51.612][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.613][info][talledLocalContainer] Unknown.anonymous(Unknown Source) [14:03:51.613][info][talledLocalContainer] [14:03:51.613][info][talledLocalContainer] -- 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

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

12 years, 4 months

3
19
0 / 0

[JBoss JIRA] (TEIID-2081) Cannot break the continuous execution

by Andriy Rokhmanov (JIRA)

12 years, 4 months

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

12 years, 4 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2012