July 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2037) Security context is not propagated correctly between Teiid engine and data sources

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2037: ----------------------------------- Summary: Security context is not propagated correctly between Teiid engine and data sources Key: TEIID-2037 URL: https://issues.jboss.org/browse/TEIID-2037 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.7, 7.6, 7.5, 7.4.1, 7.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 7.7.1 Security Context is not correctly propagated when used in remote connections (JDBC, ODBC) (Local connections OK) between Teiid Engine threads and rest of the system. The initial authentication is fine. This only poses issue with "CallerIdentityLoginModule" used in the data sources or any custom connectors that depend upon the authentication credentials that read off the executing thread. -- 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
14
0 / 0

[JBoss JIRA] (TEIID-2030) Enable the availablity of VDB classloader in the ExecutionContext/CommandContext

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2030: ----------------------------------- Summary: Enable the availablity of VDB classloader in the ExecutionContext/CommandContext Key: TEIID-2030 URL: https://issues.jboss.org/browse/TEIID-2030 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 With the development of object based translators it is required that they have access to a class loader where the object library is defined. Extend the ExecutionContext and commandContext interface to provide the classloader of the VDB, which provides the libraries defined with "lib" property. -- 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-2016) Query errors occur if 2 VDBs have the same named data roles

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-2016: -------------------------------------- Summary: Query errors occur if 2 VDBs have the same named data roles Key: TEIID-2016 URL: https://issues.jboss.org/browse/TEIID-2016 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4.1 Reporter: Debbie Steigner Assignee: Steven Hawkins Customer deployed 2 VDBs, each having a data role of the same name. When he queries the one vdb, it errors with an object doesn't exist. The object referred to is in the other vdb. -- 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
3
0 / 0

[JBoss JIRA] (TEIID-1996) Create Operation in JON/Admin Console to Retrieve Query Plan

by Ted Jones (JIRA)

Ted Jones created TEIID-1996: -------------------------------- Summary: Create Operation in JON/Admin Console to Retrieve Query Plan Key: TEIID-1996 URL: https://issues.jboss.org/browse/TEIID-1996 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin Reporter: Ted Jones Assignee: Ted Jones Need to create an operation to retrieve the query plan for a request. See TEIID-1985. -- 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
4
0 / 0

[JBoss JIRA] (TEIID-2010) Remove the rewrite of between clause with compare criteria for translator pushdowns.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2010: ----------------------------------- Summary: Remove the rewrite of between clause with compare criteria for translator pushdowns. Key: TEIID-2010 URL: https://issues.jboss.org/browse/TEIID-2010 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.7 Reporter: Ramesh Reddy Assignee: Steven Hawkins Between predicates are converted by the rewriter to => and <=, see the JavaDoc for supportsBetweenCriteria - it was only left for backwards capatiblity and should probably be removed for Teiid 8. -- 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
5
0 / 0

[JBoss JIRA] (TEIID-1868) Internal Materialized View - Load/Refresh and Assertion Failed

by John Tan (Created) (JIRA)

Internal Materialized View - Load/Refresh and Assertion Failed -------------------------------------------------------------- Key: TEIID-1868 URL: https://issues.jboss.org/browse/TEIID-1868 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4, 7.3 Environment: Windows Server 2008 R2 64 bits, JBoss EAP 5.1 Reporter: John Tan Assignee: Steven Hawkins We have about 20 tables in materialized view (internal with cache hint - /*+ cache(ttl:14400000) */). 2 dreaded behaviours: 1. On start up with application (application starts hitting app), certain query will cause ASSERTION FAILED 2. On reloading cache, teiid starts to fails with same behaviour. 2011-12-14 18:26:40,201 WARN [org.teiid.CONNECTOR] (Worker2228_QueryProcessorQueue1132419) Connector worker process failed for atomic-request=mCMnhhZ9fLcU.100.3.334092 [JDBCExecutionException] 0: Error Code:0 Message:'ASSERTION FAILED: expected reference to be not null' error executing statement(s):[....] 1 [TeiidSQLException]ASSERTION FAILED: expected reference to be not null 2 [TeiidException]ASSERTION FAILED: expected reference to be not null 3 [AssertionError]ASSERTION FAILED: expected reference to be not null at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263) 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: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:662) Caused by: org.teiid.jdbc.TeiidSQLException: ASSERTION FAILED: expected reference to be not null at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:497) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:214) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) ... 12 more Caused by: [TeiidException]ASSERTION FAILED: expected reference to be not null 1 [AssertionError]ASSERTION FAILED: expected reference to be not null at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177) at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:557) at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:335) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:218) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) ... 6 more Caused by: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null at org.teiid.core.util.Assertion.failed(Assertion.java:73) at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:366) at org.teiid.query.tempdata.TempTable$QueryTupleSource.<init>(TempTable.java:141) at org.teiid.query.tempdata.TempTable$QueryTupleSource.<init>(TempTable.java:130) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:410) at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:402) at org.teiid.query.tempdata.TempTableDataManager.registerQuery(TempTableDataManager.java:437) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:182) at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:170) at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:197) at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:118) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95) at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:138) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:72) at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:250) at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:152) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:134) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115) at org.teiid.query.processor.relational.SubqueryAwareEvaluator.evaluateSubquery(SubqueryAwareEvaluator.java:129) at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:445) at org.teiid.query.eval.Evaluator.evaluateTVL(Evaluator.java:218) at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:203) at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:102) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:162) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70) at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69) at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82) at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:214) at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:168) at org.teiid.query.processor.relational.SortNode.sortPhase(SortNode.java:96) at org.teiid.query.processor.relational.SortNode.nextBatchDirect(SortNode.java:85) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:274) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:161) 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) ... 7 more 2011-12-14 18:26:40,201 WARN [org.teiid.PROCESSOR] (Worker2205_QueryProcessorQueue1132421) Processing exception 'Error Code:0 Message:Error Code:0 Message:'ASSERTION FAILED: expected reference to be not null' error executing statement(s): [....] for request mCMnhhZ9fLcU.100. Exception type org.teiid.core.TeiidProcessingException thrown from org.teiid.core.util.Assertion.failed(Assertion.java:73). Enable more detailed logging to see the entire stacktrace. -- 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

8
32
0 / 0

[JBoss JIRA] (TEIID-2018) VDB resources are not associated

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2018: ------------------------------------- Summary: VDB resources are not associated Key: TEIID-2018 URL: https://issues.jboss.org/browse/TEIID-2018 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.0 The vdb resource entries are not being associated to the runtime vdb state, thus schema lookups will throw hard errors. -- 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-2027) maxSourceRows being incorrectly applied when query returns less rows than the limit

by Graeme Gillies (JIRA)

Graeme Gillies created TEIID-2027: ------------------------------------- Summary: maxSourceRows being incorrectly applied when query returns less rows than the limit Key: TEIID-2027 URL: https://issues.jboss.org/browse/TEIID-2027 Project: Teiid Issue Type: Bug Affects Versions: 7.6 Environment: Teiid 7.6 running on JBoss EAP 5.1 on RHEL 5. JDK is java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.25.1.10.6.el5_8-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Reporter: Graeme Gillies Assignee: Steven Hawkins We have a user who is trying to run a particularly large query against our VDB but is getting the error {code} > ERROR MESSAGE: > BugzillaDS: The number of result rows has exceeded the maximum result > rows "100,000" > DETAIL: org.teiid.jdbc.TeiidSQLException: BugzillaDS: The number of > result rows has exceeded the maximum result rows "100,000" {code} Which seems fairly self explanatory, as we do have maxSourceRows set to 100000 in teiid-jboss-beans.xml. Unfortunately though, the query in question should be returning only about 2000 rows, so it shouldn't be hitting this error at all. In fact, I am able to replicate this problem with the following simple script {noformat} #!/usr/bin/env python import psycopg2 conn = psycopg2.connect("host=vdb.example.com port=35432 dbname=MyVDB user=user password=password") cursor = conn.cursor() query = "SELECT bugs.bug_id, bugs.creation_ts FROM Bugzilla.bugs WHERE bugs.bug_id IN (%s)" % ','.join(map(str, range(1,1002))) cursor.execute(query) rows = cursor.fetchall() cols = [t[0] for t in cursor.description] for row in rows: print ", ".join(["%s = %s" % (col, value) for col, value in zip(cols, row)]) conn.close() {noformat} If I change {code} query = "SELECT bugs.bug_id, bugs.creation_ts FROM Bugzilla.bugs WHERE bugs.bug_id IN (%s)" % ','.join(map(str, range(1,1002))) {code} to {code} query = "SELECT bugs.bug_id, bugs.creation_ts FROM Bugzilla.bugs WHERE bugs.bug_id IN (%s)" % ','.join(map(str, range(1,1001))) {code} The code works fine, so it seems that there is some 1000 row limit somewhere that Is being used instead of the value we set (100000) -- 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-1943) Create a JDBC Wrapper that will enable the creation of tables from a Java API via importing

by Van Halbert (JIRA)

Van Halbert created TEIID-1943: ---------------------------------- Summary: Create a JDBC Wrapper that will enable the creation of tables from a Java API via importing Key: TEIID-1943 URL: https://issues.jboss.org/browse/TEIID-1943 Project: Teiid Issue Type: Feature Request Components: Tools Reporter: Van Halbert Assignee: Van Halbert Create a JDBC wrapper that will enable someone to create tables from their Java API. This will assist in the modeling effort in order to use the Coherence translator. Additionally, this could be useful when Infinispan is supported. -- 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
4
0 / 0

[JBoss JIRA] (TEIID-1977) Prepared Statements on ODBC ending with failure

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1977: ----------------------------------- Summary: Prepared Statements on ODBC ending with failure Key: TEIID-1977 URL: https://issues.jboss.org/browse/TEIID-1977 Project: Teiid Issue Type: Bug Affects Versions: 7.7 Reporter: Ramesh Reddy Assignee: Steven Hawkins When a preprared statement executed on the ODBC transport, the below error occurs. This is with the PG's latest ODBC driver, not 8.4.200 that been validate current code against. Message: Error Code:ERR.015.008.0039 Message:The function 'pg_get_expr(d.adbin, d.adrelid)' is an unknown form. Check that the function name and number of arguments is correct. -- 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
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2012