March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4017) EXECUTE IMMEDIATE in anonymous procedure ignores permissions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4017?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4017: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1314863|https://bugzilla.redhat.com/show_bug.cgi?id=1314863] from ASSIGNED to MODIFIED > EXECUTE IMMEDIATE in anonymous procedure ignores permissions > ------------------------------------------------------------ > > Key: TEIID-4017 > URL: https://issues.jboss.org/browse/TEIID-4017 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12 > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.0, 8.12.5, 8.13.2 > > > I've found a bug when executing a query in the EXECUTE IMMEDIATE clause. It ignores permissions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4049) OData 4 query hangs in test run

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4049: ------------------------------------- Summary: OData 4 query hangs in test run Key: TEIID-4049 URL: https://issues.jboss.org/browse/TEIID-4049 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins During the run of: org.teiid.olingo.TestODataIntegration.testExpandSimple(TestODataIntegration.java:988) The server seems to be in an indefinite wait state: "qtp1207140081-380" #380 prio=5 os_prio=0 tid=0x00007f7c94bbb800 nid=0x3642 in Object.wait() [0x00007f7c6a6cc000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:287) - locked <0x0000000770e1c130> (a org.teiid.dqp.internal.process.RequestWorkItem) at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:313) at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:245) at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:190) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260) at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:188) at com.sun.proxy.$Proxy15.executeRequest(Unknown Source) at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:673) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:539) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260) at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73) at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:228) at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:347) at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:167) at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:302) at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:245) at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:117) at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:65) at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:50) Just trying to run the test or the whole test class in isolation through many iterations has not reproduced this, so I'm logging this for now in hopes that if others see this we may get more details as to when it occurs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4015) Error or incorrect value when there is a conflict between local and correlated names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4015?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4015: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1314538|https://bugzilla.redhat.com/show_bug.cgi?id=1314538] from ASSIGNED to MODIFIED > Error or incorrect value when there is a conflict between local and correlated names > ------------------------------------------------------------------------------------ > > Key: TEIID-4015 > URL: https://issues.jboss.org/browse/TEIID-4015 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > With a query such as: > select e1, (select e1 from (select t1.e1 from pm1.g1 as t1) as t2 where t2.e1 = t1.e1) from pm2.g1 as t1 > The correlated reference to t1.e1 will get evaulated as if it were a local value from pm1.g1 as t1 instead. This is because the evaluator doesn't immediately look for the context value, but rather calls to internalEvaluate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4015) Error or incorrect value when there is a conflict between local and correlated names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4015?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4015: --------------------------------- Fix Version/s: 8.7.5.6_2 > Error or incorrect value when there is a conflict between local and correlated names > ------------------------------------------------------------------------------------ > > Key: TEIID-4015 > URL: https://issues.jboss.org/browse/TEIID-4015 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > With a query such as: > select e1, (select e1 from (select t1.e1 from pm1.g1 as t1) as t2 where t2.e1 = t1.e1) from pm2.g1 as t1 > The correlated reference to t1.e1 will get evaulated as if it were a local value from pm1.g1 as t1 instead. This is because the evaluator doesn't immediately look for the context value, but rather calls to internalEvaluate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4008: --------------------------------- Fix Version/s: 8.7.5.6_2 > Sending teiid varbinary value (x'') to Microsoft SQL Server errors > ------------------------------------------------------------------ > > Key: TEIID-4008 > URL: https://issues.jboss.org/browse/TEIID-4008 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > When sending a query to Microsoft SQL Server with a varbinary in criteria: > select * from debBinary where ipv6= x'FFFF6BBE85D8' > It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8': > [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8' > [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4007) Unparseable model name if user changes odata4 context root

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4007?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4007: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1313626|https://bugzilla.redhat.com/show_bug.cgi?id=1313626] from MODIFIED to ON_QA > Unparseable model name if user changes odata4 context root > ---------------------------------------------------------- > > Key: TEIID-4007 > URL: https://issues.jboss.org/browse/TEIID-4007 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Juraj Duráni > Fix For: 9.0, 8.12.5, 8.13.2 > > > If user changes root context of odata4 service, Teiid does not parse model name from the URI and throws TEIID16022 instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4008) Sending teiid varbinary value (x'') to Microsoft SQL Server errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4008?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4008: ------------------------------------------------ jolee(a)redhat.com changed the Status of [bug 1313407|https://bugzilla.redhat.com/show_bug.cgi?id=1313407] from NEW to MODIFIED > Sending teiid varbinary value (x'') to Microsoft SQL Server errors > ------------------------------------------------------------------ > > Key: TEIID-4008 > URL: https://issues.jboss.org/browse/TEIID-4008 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.2.6_2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2, 8.7.5.6_2 > > > When sending a query to Microsoft SQL Server with a varbinary in criteria: > select * from debBinary where ipv6= x'FFFF6BBE85D8' > It pushes the criteria to Microsoft SQL Server, but as X'FFFF6BBE85D8'[1] so Microsoft gives the syntax error[2] and needs to just be select * from debBinary where ipv6= 'FFFF6BBE85D8': > [1]14:26:08,951 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8) Source-specific command: SELECT g_0."id", g_0."ipv6" FROM "bqt2"."dbo"."debbinary" g_0 WHERE g_0."ipv6" = X'FFFF6BBE85D8' > [2] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'FFFF6BBE85D8'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3983: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1309582|https://bugzilla.redhat.com/show_bug.cgi?id=1309582] from MODIFIED to ON_QA > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4003) Vertica and DB2 translators use incorrect push down of WEEK function

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4003?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4003: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1312264|https://bugzilla.redhat.com/show_bug.cgi?id=1312264] from MODIFIED to ON_QA > Vertica and DB2 translators use incorrect push down of WEEK function > -------------------------------------------------------------------- > > Key: TEIID-4003 > URL: https://issues.jboss.org/browse/TEIID-4003 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > TEIID-3282 changed the semantics of the WEEK function to use the iso behaviour. > The Vertica database has WEEK_ISO function that returns the iso week, but the translator does not have that alias set. > This results in the query (the datevalue in question is 2000-12-31) > {code:sql} > select week(datevalue) from source.largea where intkey = 365 > {code} > to return 54, when the correct value is 52. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4024) Server fails to shutdown if vdb with REST service generation is deployed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4024?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4024: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1315279|https://bugzilla.redhat.com/show_bug.cgi?id=1315279] from MODIFIED to ON_QA > Server fails to shutdown if vdb with REST service generation is deployed > ------------------------------------------------------------------------ > > Key: TEIID-4024 > URL: https://issues.jboss.org/browse/TEIID-4024 > Project: Teiid > Issue Type: Bug > Components: VDB > Affects Versions: 8.12.5 > Environment: DV 6.3 ER1 > Reporter: Filip Elias > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.x > > Attachments: nosource-vdb.xml, server_trace.log > > > DV sometimes won't stop if vdb with REST service generation is deployed. > Server log is in the attachment. > When the server is killed and started again, it will stop correctly. > The issue is random. Server fails to stop in 50% of cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016