January 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1253) Allow for cache scope to be set in the cache hint

by Steven Hawkins (JIRA)

Allow for cache scope to be set in the cache hint ------------------------------------------------- Key: TEIID-1253 URL: https://jira.jboss.org/browse/TEIID-1253 Project: Teiid Issue Type: Feature Request Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 In some circumstances the cache scope may need to be set in the cache hint to override the detected scope. The cache hint would need something like scope:{session|user|global} and we would need to ensure that the analysis log / debug log includes sufficient information to see what scope is in use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1388) Appears to be a limit of only one functional SalesForce connector in Teiid at a time.

by John Doyle (JIRA)

Appears to be a limit of only one functional SalesForce connector in Teiid at a time. ------------------------------------------------------------------------------------- Key: TEIID-1388 URL: https://issues.jboss.org/browse/TEIID-1388 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.1.1 Environment: Teiid 7.1.1 in EDS ER5, JBDS Beta2, RHEL 5.1 Reporter: John Doyle Assignee: John Doyle Priority: Blocker It appears they only one SalesForce connector can be run at a time. If you preview a model from Designer and there are no SF connections in Teiid, it works. When you create a DS for the VDB and deploy, the VDB cannot get connections from SalesForce. If you delete the preview VDB and Datasource, then the deployed VDB begins working. I originally suspected that the problem might be that we are running out of connections; SalesForce limits you to 5 simultaneous connections per username/password. But I deployed the two DataSources with different credentials, and the result did not change. Need to investigate more. Think that we do need to default the SF DS to a pool of 1 and then doc that it should be bumped to 5 for production. The current default is 10, and that should never be. Even 5 will exhaust the limit with just a preview connection. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIID-1338) Add transitive join conditions across sources

by Steven Hawkins (JIRA)

Add transitive join conditions across sources --------------------------------------------- Key: TEIID-1338 URL: https://jira.jboss.org/browse/TEIID-1338 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.3 A situation such as from a, b, c where a.x = b.x and a.x = c.x such that b and c are on a different source than a, it would be good to also use transitive condition b.x = c.x. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1267) Add support for non-pushdown subquery evaluation on update statements

by Debbie Steigner (JIRA)

Add support for non-pushdown subquery evaluation on update statements --------------------------------------------------------------------- Key: TEIID-1267 URL: https://jira.jboss.org/browse/TEIID-1267 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Debbie Steigner Assignee: Steven Hawkins Please add support for non-pushdown subquery evaluation on INSERT/UPDATE/DELETE statements -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1227) Lob values should be cachable

by Steve Hawkins (JIRA)

Lob values should be cachable ----------------------------- Key: TEIID-1227 URL: https://jira.jboss.org/browse/TEIID-1227 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.2 Lob values from any source, not just XML document models should be cachable. Typically this would need to be "by value" so a copy of the lob will need to be created in the buffermanager. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1408) SalesForce.com - Unable to get managed connection - java.lang.NullPointerException

by Warren Gibson (JIRA)

SalesForce.com - Unable to get managed connection - java.lang.NullPointerException ---------------------------------------------------------------------------------- Key: TEIID-1408 URL: https://issues.jboss.org/browse/TEIID-1408 Project: Teiid Issue Type: Bug Components: Salesforce Connector Environment: Linux server, SOA-P ER6 Reporter: Warren Gibson Assignee: Steven Hawkins Connection to SalesForce.com with the attached SalesForce VDB and DS file works in ER5 but is failing in ER6. It is failing with the NullPointer below. If the URL property in the DS file is removed a connection can be made and queries work successfully. 2010-12-21 13:01:26,835 DEBUG [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue237) [Ljava.lang.Object;@1b66915 [TeiidProcessingException]Unable to get managed connection for salesforce 1 [TranslatorException]Unable to get managed connection for salesforce 2 [ResourceException]Unable to get managed connection for salesforce 3 [JBossResourceException]Unexpected throwable while trying to create a connection: null; - nested throwable: (java.lang.NullPointerException) 4 [NullPointerException] at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:371) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:214) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:154) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:107) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:150) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: [TranslatorException]Unable to get managed connection for salesforce 1 [ResourceException]Unable to get managed connection for salesforce 2 [JBossResourceException]Unexpected throwable while trying to create a connection: null; - nested throwable: (java.lang.NullPointerException) 3 [NullPointerException] at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:146) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:198) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108) ... 6 more Caused by: javax.resource.ResourceException: Unable to get managed connection for salesforce at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:381) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941) at org.teiid.resource.spi.WrappedConnectionFactory.getConnection(WrappedConnectionFactory.java:53) at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:144) ... 12 more Caused by: org.jboss.resource.JBossResourceException: Unexpected throwable while trying to create a connection: null; - nested throwable: (java.lang.NullPointerException) at org.jboss.resource.JBossResourceException.rethrowAsResourceException(JBossResourceException.java:61) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:304) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:690) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404) ... 17 more Caused by: java.lang.NullPointerException at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.login(SalesforceConnectionImpl.java:111) at org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.<init>(SalesforceConnectionImpl.java:76) at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:76) at org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory$1.getConnection(SalesForceManagedConnectionFactory.java:71) at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:70) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:639) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:273) ... 19 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1433) Temp tables should support count(*)

by Steven Hawkins (JIRA)

Temp tables should support count(*) ----------------------------------- Key: TEIID-1433 URL: https://issues.jboss.org/browse/TEIID-1433 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.3 It would be good to have temp table implement count(*) directly rather than relying on iteration. If there is a condition, then we'll still have to iterate the results - but at least we won't have to create a buffer backed form of the results in the case of an updatable table. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1357) Provide an example of an ODBC ds file to be used with a JDBC-ODBC bridge connection

by Warren Gibson (JIRA)

Provide an example of an ODBC ds file to be used with a JDBC-ODBC bridge connection ------------------------------------------------------------------------------------ Key: TEIID-1357 URL: https://jira.jboss.org/browse/TEIID-1357 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.1 Environment: Teiid using JDBC-ODBC bridge connection to a vdb source Reporter: Warren Gibson Assignee: Steven Hawkins Provide an example of an ODBC ds file for users to reference when connecting to a source through the JDBC-ODBC bridge. The ds file used in testing Excel is listed below: <?xml version="1.0" encoding="UTF-8"?> <datasources> <no-tx-datasource> <jndi-name>ExcelDS</jndi-name> <connection-url>jdbc:odbc:Driver={Microsoft Excel Driver (*.xls)};Dbq=e:\ODBC_Testing\ODBC\EmpData.xls</connection-url> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class> <transaction-isolation>TRANSACTION_NONE</transaction-isolation> <min-pool-size>1</min-pool-size> <max-pool-size>1</max-pool-size> <idle-timeout-minutes>5</idle-timeout-minutes> </no-tx-datasource> </datasources> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1407) Client code fails while inserting "lobs" in few situations

by Ramesh Reddy (JIRA)

Client code fails while inserting "lobs" in few situations ---------------------------------------------------------- Key: TEIID-1407 URL: https://issues.jboss.org/browse/TEIID-1407 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.2, 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical There were few different lob issues surfaced while inserting a blob into database using the Teiid. 1) Using "javax.sql.rowset.serial.SerialBlob" to construct a blob, and using stmt.setBlob(int, blob) on prepared statement ended up with "broken pipe" error and terminated the client connection when the blob size was bigger than a 1 MB. 2) Using "org.teiid.core.types.ClobImpl" with constructor " new ClobImpl(int, InputStreamFactory)" resulted in the java.io.NotSerializableException: exception. 3) Using simple stmt.setBlob(int, inputstream), also ended up with same java.io.NotSerializableException: exception. Currently only option is to use (1) and making sure that Objects are not bigger than 1 MB. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1372) Change the default Teiid user from "admin" to something else

by Ramesh Reddy (JIRA)

Change the default Teiid user from "admin" to something else ------------------------------------------------------------ Key: TEIID-1372 URL: https://jira.jboss.org/browse/TEIID-1372 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.2 Reporter: Ramesh Reddy Currently Teiid default user is "admin" with password "teiid", also the Admin Console's default user name is "admin" with password "admin". This is a confusion point with users in differentiating the Admin user from default Teiid user. Should consider changing the default user to something else. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

8
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2011