May 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1984) GetUpdated and GetDeleted SF procedures should be supported in dynamic vdbs

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1984: ------------------------------------- Summary: GetUpdated and GetDeleted SF procedures should be supported in dynamic vdbs Key: TEIID-1984 URL: https://issues.jboss.org/browse/TEIID-1984 Project: Teiid Issue Type: Enhancement Components: Salesforce Connector Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The SalesforceExecutionFactory.getMetadata method does not populate the getDeleted and getUpdated procedures. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2050) Move the default login properties file to "configuration" directory

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2050: ----------------------------------- Summary: Move the default login properties file to "configuration" directory Key: TEIID-2050 URL: https://issues.jboss.org/browse/TEIID-2050 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 Currently the teiid-security-users.properties teiid-security-roles.properties properties are defined inside the "modules" directory under "teiid", which is obscure and hard to find. Move them to the configuration directory along side application-users.properties file. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2046) StaxSource is not supported for validation, VDB deployment fails

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2046: ----------------------------------- Summary: StaxSource is not supported for validation, VDB deployment fails Key: TEIID-2046 URL: https://issues.jboss.org/browse/TEIID-2046 Project: Teiid Issue Type: Bug Reporter: Ramesh Reddy Assignee: Ramesh Reddy "apache.xerces" is used by default in the AS7 as the chosen jaxp library, and it does not support StaxSource as the Validator input. Consider using some other type of source like StreamSource. Caused by: java.lang.IllegalArgumentException: Source parameter of type 'javax.xml.transform.stax.StAXSource' is not accepted by this validator. at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:119) at javax.xml.validation.Validator.validate(Validator.java:127) [rt.jar:1.6.0_26] at org.teiid.adminapi.impl.VDBMetadataParser.validate(VDBMetadataParser.java:94) at org.teiid.jboss.VDBParserDeployer.parseVDBXML(VDBParserDeployer.java:111) at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:88) at org.teiid.jboss.VDBParserDeployer.scanVDB(VDBParserDeployer.java:83) at org.teiid.jboss.VDBParserDeployer.deploy(VDBParserDeployer.java:72) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] (TEIID-2058) Optimization places WHERE clause incorrectly when criteria not supplied for tables with joins

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2058: ------------------------------------ Summary: Optimization places WHERE clause incorrectly when criteria not supplied for tables with joins Key: TEIID-2058 URL: https://issues.jboss.org/browse/TEIID-2058 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Johnathon Lee Assignee: Steven Hawkins Reproducible behavior with the following simplified query [1] Avoiding the error by including non-restricting criteria on tables not represented in the WHERE EXISTS clause [2]. ie: there seems to be a problem in the Optimization that writing the query similar to [2] will avoid. [1] SELECT 'X' as CMR_BPR_ID2 FROM Y93 INNER JOIN AG5 ON 1 = 1 LEFT OUTER JOIN MFSMFL.I58 as I58 ON 1 = 1 WHERE EXISTS (SELECT 'Y' FROM BH0 WHERE AG5.CONSENT_CLIENT_ID = 1 AND Y93.CMR_BPR_ID2 = 1 ) [2] SELECT 'X' as CMR_BPR_ID2 FROM Y93 INNER JOIN AG5 ON 1 = 1 LEFT OUTER JOIN MFSMFL.I58 as I58 ON 1 = 1 WHERE EXISTS (SELECT 'Y' FROM BH0 WHERE AG5.CONSENT_CLIENT_ID = 1 AND Y93.CMR_BPR_ID2 = 1 AND I58.FUND_CODE like '%') -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] (TEIID-2049) NPE during select call on a materialized table

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2049: ----------------------------------- Summary: NPE during select call on a materialized table Key: TEIID-2049 URL: https://issues.jboss.org/browse/TEIID-2049 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 This is a regression because of the TEIID-1981. {code} 17:44:22,307 ERROR [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue19) TEIID30019 Unexpected exception for request qruejSyXY+pR.0: java.lang.NullPointerException at org.teiid.query.optimizer.relational.RelationalPlanner.resolveVirtualGroup(RelationalPlanner.java:1233) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.buildTree(RelationalPlanner.java:836) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:737) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:696) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.generatePlan(RelationalPlanner.java:490) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:180) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:188) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:429) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.Request.processRequest(Request.java:449) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:534) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:278) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:217) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:241) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) [teiid-engine-8.0.0.Final.jar:8.0.0.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [rt.jar:1.6.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [rt.jar:1.6.0_05] at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_05] {code} -- 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, 7 months

2
2
0 / 0

[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

13 years, 7 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

13 years, 7 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

13 years, 7 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

13 years, 7 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

13 years, 7 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2012