September 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2189) Can the behaviour of the || operator to use concat2 to mirror the oracle functionality be made configurable

by Van Halbert (JIRA)

Van Halbert created TEIID-2189: ---------------------------------- Summary: Can the behaviour of the || operator to use concat2 to mirror the oracle functionality be made configurable Key: TEIID-2189 URL: https://issues.jboss.org/browse/TEIID-2189 Project: Teiid Issue Type: Enhancement Components: JDBC Connector, Server Affects Versions: 7.4.4 Reporter: Van Halbert Assignee: Steven Hawkins Is it possible to make configurable the ability to switch the behaviour of the || operator to use concat2 in order to mirror the oracle functionality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] (TEIID-2095) Cannot use deployed WAR with HTTPBasic authentication

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2095: ---------------------------------- Summary: Cannot use deployed WAR with HTTPBasic authentication Key: TEIID-2095 URL: https://issues.jboss.org/browse/TEIID-2095 Project: Teiid Issue Type: Bug Components: SOAP Services Affects Versions: 7.7.1 Environment: RHEL6 (SOA 5.3 ER5) Reporter: Paul Nittel Assignee: Steven Hawkins Fix For: 7.7.1 I created a WAR which specifies HTTPBasic security. My WAR definition specifies a role and the default realm (teiid-security). On the server, my datasource specifies PassthroughAuthentication=true. I have tried Security Deployment Types of None and Domain (where I specified the domain as "teiid-security"). When I try to access the WSDL from the Web Services console, I am not being prompted for a username and password; I am just being denied (403). I've tried clearing the browser cache and bouncing the server. I'm attaching the datasource and WAR files. -- 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, 3 months

5
23
0 / 0

[JBoss JIRA] (TEIID-2207) RHQ Plugin gets NPE when getting requests for a VDB

by Paul Nittel (JIRA)

Paul Nittel created TEIID-2207: ---------------------------------- Summary: RHQ Plugin gets NPE when getting requests for a VDB Key: TEIID-2207 URL: https://issues.jboss.org/browse/TEIID-2207 Project: Teiid Issue Type: Feature Request Affects Versions: 7.7.1 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: server.log Using RHQ while a long query was executing, I used the VDB's "View VDB Requests" and received no information in the UI. The server log contained the attached exception and stack trace. java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'getRequestsUsingVDB' on component 'RuntimeEngineDeployer' with parameters [SimpleMetaType:java.lang.String:TpcrVdb, SimpleMetaType:int:1]. at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:103) at sun.reflect.GeneratedMethodAccessor661.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
9
0 / 0

[JBoss JIRA] (TEIID-2209) Temp logic should support the array type

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2209: ------------------------------------- Summary: Temp logic should support the array type Key: TEIID-2209 URL: https://issues.jboss.org/browse/TEIID-2209 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor If a temp table is made the dependent side of a multi-column dependent join, the index logic should support the array type for more efficient processing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2205) Temp table and procedure block transactions issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2205: ------------------------------------- Summary: Temp table and procedure block transactions issue Key: TEIID-2205 URL: https://issues.jboss.org/browse/TEIID-2205 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 8.2 The Request class is not correctly setting the transactioncontext on the commandcontext, so downstream transaction logic in temp tables and procedure blocks will not work properly. For procedure blocks an exception may occur if an existing local/global transaction has been started, and temp table work will fail to isolate correctly and not rollback. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2203) CLONE - Add support for function based indexes on materialized views

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2203: ------------------------------------- Summary: CLONE - Add support for function based indexes on materialized views Key: TEIID-2203 URL: https://issues.jboss.org/browse/TEIID-2203 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 Teiid materialized views should support function based indexes to improve performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2194) Allow the mat view cache hint to be specified via a property

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2194: ------------------------------------- Summary: Allow the mat view cache hint to be specified via a property Key: TEIID-2194 URL: https://issues.jboss.org/browse/TEIID-2194 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 8.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Setting the mat cache hint via a property is useful so that it can be changed independently of the view definition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2192) Failure to access Oracle data source with column names enclosed in double quotes

by Hisanobu Okuda (JIRA)

Hisanobu Okuda created TEIID-2192: ------------------------------------- Summary: Failure to access Oracle data source with column names enclosed in double quotes Key: TEIID-2192 URL: https://issues.jboss.org/browse/TEIID-2192 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 7.4.4 Environment: EDS 5.2.0 Reporter: Hisanobu Okuda Assignee: Steven Hawkins EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when i run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error. For example, 1. create table and views as shown below in Oracle database {code} create table test(recno number, ref_no varchar2(4000)); create or replace view test_v as select recno as "Rec_Item_Number", ref_no as "bom_ref_no." from test; {code} 2. Import test_v data source view into JBoss developer studio 3. deploy and run the query against TEST_V:- Then, the following exception is thrown:- {code} 2012-09-05 08:34:39,386 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Imx1VPWhia7G.6.0.0 org.teiid.translator.jdbc.JDBCExecutionException: Error Code:1747 Message:'ORA-01747: invalid user.table.column, table.column, or column specification ' error executing statement(s): [Prepared Values: [] SQL: SELECT c_0, c_1 FROM (SELECT g_0.Rec_Item_Number AS c_0, g_0.bom_ref_no. AS c_1 FROM "EII_CACHE"."TEST_V" g_0) WHERE ROWNUM <= 100] at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:90) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:276) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292) 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) Caused by: java.sql.SQLSyntaxErrorException: ORA-01747: invalid user.table.column, table.column, or column specification at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3628) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1493) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:342) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:86) ... 13 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2184) Locale issues

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2184: ------------------------------------- Summary: Locale issues Key: TEIID-2184 URL: https://issues.jboss.org/browse/TEIID-2184 Project: Teiid Issue Type: Quality Risk Components: Common Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.2 Some tests are specific to the en us locale. Also the monthname and dayname functions are hard coded to en, which is not consistent with our default logic of relying on the system locale for parse/format handling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2012