June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3499) IllegalStateException wihle using DataNotAvailableException.NO_POLLING

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3499?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3499: --------------------------------------- > it is possible that dataAvailable() is being called after null is returned from next() That's shouldn't be an issue. The side effect of dataAvailable should just be to wake up the processing thread and put it into the more work state. The only way I can see this happening is if there are two processing threads on the work item, so that one of them can transition it to idle/working and cause this exception. If however your usage of the connection is single threaded, that shouldn't happen. > IllegalStateException wihle using DataNotAvailableException.NO_POLLING > ---------------------------------------------------------------------- > > Key: TEIID-3499 > URL: https://issues.jboss.org/browse/TEIID-3499 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.11 > Reporter: Mark Addleman > Assignee: Steven Hawkins > > java.lang.IllegalStateException: Must be in MORE_WORK > at org.teiid.dqp.internal.process.AbstractWorkItem.startProcessing(AbstractWorkItem.java:70) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:48) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) > at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298) > at sun.reflect.GeneratedMethodAccessor37.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:175) > 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:173) > at com.sun.proxy.$Proxy14.executeRequest(Unknown Source) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527) > at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) > at com.ca.apm.server.teiid.REPL.printQuery(REPL.java:90) > at com.ca.apm.server.teiid.REPL.printQuery(REPL.java:116) > at com.ca.apm.server.teiid.REPL.issue62_no_timerangekey(REPL.java:713) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3512) produce a lighter weight embedded kit

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3512: ------------------------------------- Summary: produce a lighter weight embedded kit Key: TEIID-3512 URL: https://issues.jboss.org/browse/TEIID-3512 Project: Teiid Issue Type: Feature Request Components: Embedded Reporter: Steven Hawkins The embedded kit should be a small as possible, and it should be clear/easy to get dependency sets for each optional piece of functionality. This could include using maven to pull artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-3511: ------------------------------------- I see that the debug log changed the query a little. In the original query the BITAND part was like this: BITAND(phr.status,2) <> 2 > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Bram Gadeyne updated TEIID-3511: -------------------------------- Attachment: debugplan_bitand_correct.txt debugplan_nobitand_correct.txt Correct Files > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3507) Matview vdb start/stop scripts are not cluster safe

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3507?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3507: ---------------------------------- Fix Version/s: 8.12 > Matview vdb start/stop scripts are not cluster safe > --------------------------------------------------- > > Key: TEIID-3507 > URL: https://issues.jboss.org/browse/TEIID-3507 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > The on vdb start/stop scripts will run on each cluster member start. This needs to be cluster safe or documented that it won't be safe. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3503) Development with Embedded teiid should not require dependency on EAP

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3503: ---------------------------------- Fix Version/s: 8.12 (was: 8.11) > Development with Embedded teiid should not require dependency on EAP > -------------------------------------------------------------------- > > Key: TEIID-3503 > URL: https://issues.jboss.org/browse/TEIID-3503 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Affects Versions: 8.10 > Reporter: Michael Davies > Assignee: Ramesh Reddy > Priority: Minor > Labels: CR1 > Fix For: 8.12 > > > We are using Embedded and specifically ModelMetaData, for specifying VDB. > ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo. > For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4 > So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo. > Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3508) External mat view without ttl behavior

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3508?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3508: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > External mat view without ttl behavior > -------------------------------------- > > Key: TEIID-3508 > URL: https://issues.jboss.org/browse/TEIID-3508 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > > When no ttl is specified an external mat view will not be loaded by the management service - but the on vdb start / stop scripts will be run. We should figure out if/when an initial load should take place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3475) Add a separate example module for embedded examples

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3475?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3475: --------------------------------------- Should we resolve this one no in favor of TEIID-3510? > Add a separate example module for embedded examples > ---------------------------------------------------- > > Key: TEIID-3475 > URL: https://issues.jboss.org/browse/TEIID-3475 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > Attachments: drools-examples.png > > > Add a separate example module for embedded examples, it will contain a runnable jar, which will load all available examples, it will also contain transaction manager, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3511: --------------------------------------- Neither plan shows the use of bitand. > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_nobitand.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Bram Gadeyne updated TEIID-3511: -------------------------------- Attachment: debugplan_bitand.txt debugplan_nobitand.txt The debug plans with and without BITAND. > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_nobitand.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015