January 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1195) Error message that a VDB was deployed in "deployed in inactive state" is insufficient for users to easily correct problem

by Paul Nittel (JIRA)

Error message that a VDB was deployed in "deployed in inactive state" is insufficient for users to easily correct problem ------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1195 URL: https://jira.jboss.org/browse/TEIID-1195 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Assignee: Steve Hawkins Attachments: server.log.zip Admittedly this stems from another bug (where VDBs with even a warning are not deployed), but the lack of details surrounding the decision to deploy in an inactive state causes confusion. Even though my logging is set to DEBUG, the server log contains no details as to why the VDB was not made active. Please see the attached log file. -- 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

13 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-1252) LOB handling strategry issues

by Steven Hawkins (JIRA)

LOB handling strategry issues ----------------------------- Key: TEIID-1252 URL: https://jira.jboss.org/browse/TEIID-1252 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 LOBs returned from sources cause executions to stay alive until the user query has been completed - this is true even if the LOB values are not returned to the user. Whenever an execution is kept alive, it's associated connection is held until the execution is closed - thus source connections may be held out of their pool indefinately. Currently each source execution will attempt to obtain a new connection from the pool, which with LOB handling will cause potentially many connections even to the same source to be held out of the their pool indefinitely. -- 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

13 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1302) Selecting data from salesforce results in a IndexOutOfBoundsException

by Wanja Pernath (JIRA)

Selecting data from salesforce results in a IndexOutOfBoundsException --------------------------------------------------------------------- Key: TEIID-1302 URL: https://jira.jboss.org/browse/TEIID-1302 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.1 Environment: Fedora 12, x86_64, java 6u21 Reporter: Wanja Pernath Assignee: Steven Hawkins Fix For: 7.1.1 After importing of the salesforce data structure via designer, connection with an EAP 5.1 runtime with Teiid7.1 installed, I get an IndexOutOfBoundsException when I am trying to do simple SELECTing of salesforce data: SELECT * from sfdc.salesforce.Opportunity o WHERE (1 = 1) and (o.Fiscal = '2011 2') and (o.Country_of_Order__c = 'Germany') Exception: 2010-10-12 20:10:32,376 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue21) Unexpected exception for request cy2xWqMIKJHq.0 java.lang.IndexOutOfBoundsException: Index: 200, Size: 200 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.loadBatch(QueryExecutionImpl.java:190) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.getRow(QueryExecutionImpl.java:165) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.next(QueryExecutionImpl.java:157) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:285) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:270) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:181) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:53) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:89) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:86) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107) 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$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) The connector only works if I am selecting data of an Account: SELECT * from sfdc.salesforce.Account WHERE (1 = 1) and Name like 'Bit%' and BillingCountry = 'Germany'; (97 results) -- 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

13 years, 4 months

3
7
0 / 0

[JBoss JIRA] Closed: (TEIID-1318) Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1318?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1318. --------------------------------- > Adminshell: Accessing VDB version results in exception: Connector worker process failed for atomic-request > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1318 > URL: https://issues.jboss.org/browse/TEIID-1318 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Len DiMaggio > Assignee: Ramesh Reddy > Fix For: 7.1.1 > > Attachments: interoperability-vdb.xml, interoperability2-vdb.xml, VDB_version_server.log > > > Server log is attached. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1343) Create a Separate Plugin for Embedded Jopr vs JON

by Ted Jones (JIRA)

Create a Separate Plugin for Embedded Jopr vs JON ------------------------------------------------- Key: TEIID-1343 URL: https://jira.jboss.org/browse/TEIID-1343 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to change the build process to create two plugin in teiid-console. One for Embedded Jopr and one for JON due to different classloading mechanisms. -- 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

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1279) Got an Unexpected exception when starting the server, after digging, I think the message should have indicated that the UDF requires static methods

by Van Halbert (JIRA)

Got an Unexpected exception when starting the server, after digging, I think the message should have indicated that the UDF requires static methods --------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1279 URL: https://jira.jboss.org/browse/TEIID-1279 Project: Teiid Issue Type: Bug Components: Server Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor Fix For: 7.1.1 When trying to start the server got this exception: Caused by: Unexpected exception while loading org.teiid.translator.jdbc.modeshape.functions.Cast.public java.lang.Object org.teiid.translator.jdbc.modeshape.functions.Cast.cast(java.lang.String,java.lang.String) with args= [class java.lang.String, class java.lang.String] at org.teiid.query.function.FunctionTree.addFunction(FunctionTree.java:315) at org.teiid.query.function.FunctionTree.addSource(FunctionTree.java:138) at org.teiid.query.function.FunctionTree.<init>(FunctionTree.java:82) at org.teiid.query.metadata.TransformationMetadata.<init>(TransformationMetadata.java:160) at org.teiid.deployers.CompositeVDB.buildTransformationMetaData(CompositeVDB.java:102) at org.teiid.deployers.CompositeVDB.update(CompositeVDB.java:84) at org.teiid.deployers.CompositeVDB.<init>(CompositeVDB.java:64) at org.teiid.deployers.VDBRepository.addVDB(VDBRepository.java:82) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:145) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:60) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) After digging into the code, I realized that the function methods are required to be static. It sure would have been nice if the error would have indicated the reason. And I can see this error happening in development. -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1283) Race condition results in bad resultset for query on union

by Howard Abrams (JIRA)

Race condition results in bad resultset for query on union ---------------------------------------------------------- Key: TEIID-1283 URL: https://jira.jboss.org/browse/TEIID-1283 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: MaxOS 10.6.4, JBoss 5.1.0 Reporter: Howard Abrams Assignee: Steven Hawkins Take a table, call it 'A', in a physical model backed by a database (DB2 on Z/OS in this case) Take a view, call it 'B', backed by a file connector >From JDBC, make the query: Select * from (select * from A union select * from B) where foo='bar'. where 'bar' is only found in B, not A. Execute the query get back a resultset: ResultSet r = statement.executeQuery(); but this code will fail with a "resultset cursor is after the last row" if ( r.next ) String foo = r.getString(1); but this code will work correctly: Thread.sleep(1000); if ( r.next ) String foo = r.getString(1); Putting the union in a materialized view also works. -- 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

13 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-1345) VDB with even one data role requires all users to have at least one mappable role

by Paul Nittel (JIRA)

VDB with even one data role requires all users to have at least one mappable role --------------------------------------------------------------------------------- Key: TEIID-1345 URL: https://jira.jboss.org/browse/TEIID-1345 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1.1 Environment: Fedora 12, SOA-P ER3, JBDS 4.0 Beta1 Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.1.1 Attachments: bwa_roleplay_MPS.zip I created a VDB which had a single data role ("dude") which was mapped to the Teiid role "webster". A user (pnittel) has the webster Teiid role and is able to access the VDB's content as specified in the "dude" data role. To allow non-dude users to access the VDB's content, I created a second data role ("non-dude") which was set using "Apply this role to All Users". Logging in as smonella (no Teiid roles), I was unable to access any data. I added a Teiid role for smonella ("fool") and then was able to access the data. It was confirmed by Teiid dev that a bug requires the creation of a role for this to work, but it should not. The smonella account should be able to access data according to the non-dude data role without a Teiid role being defined. I'll attach a Model Project Set which contains just about everything I've done here. -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1237) Stored procedures should allow for better use of inout/out/return values

by Steven Hawkins (JIRA)

Stored procedures should allow for better use of inout/out/return values ------------------------------------------------------------------------ Key: TEIID-1237 URL: https://jira.jboss.org/browse/TEIID-1237 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.2 Teiid stored procedure command or assignment statements do not typically make use of inout/out/return values (the exception is if a resultset is not returned). It would be better to allow variables to be used in inout/out positions to capture the out values. e.g. instead of call proc(1) just implicitly creating the result set to return, a = call proc(1, b) would also assign the return value to a and would set an out value to b. -- 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

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1171) Add support for the with clause

by Steve Hawkins (JIRA)

Add support for the with clause ------------------------------- Key: TEIID-1171 URL: https://jira.jboss.org/browse/TEIID-1171 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.2 The with clause would be a useful feature to take advantage of common sub expressions. -- 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

13 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2011