[JBoss JIRA] (TEIID-3499) IllegalStateException wihle using DataNotAvailableException.NO_POLLING
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3499?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-3499:
--------------------------------------
Examining my test case a little closer, it is possible that dataAvailable() is being called after null is returned from next()
> IllegalStateException wihle using DataNotAvailableException.NO_POLLING
> ----------------------------------------------------------------------
>
> Key: TEIID-3499
> URL: https://issues.jboss.org/browse/TEIID-3499
> Project: Teiid
> Issue Type: Feature Request
> 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)
8 years, 11 months
[JBoss JIRA] (TEIID-3499) IllegalStateException wihle using DataNotAvailableException.NO_POLLING
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-3499?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-3499:
--------------------------------------
I don't have a reproducible test case. Appears to be some kind of timing issue
> IllegalStateException wihle using DataNotAvailableException.NO_POLLING
> ----------------------------------------------------------------------
>
> Key: TEIID-3499
> URL: https://issues.jboss.org/browse/TEIID-3499
> Project: Teiid
> Issue Type: Feature Request
> 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)
8 years, 11 months
[JBoss JIRA] (TEIID-3499) IllegalStateException wihle using DataNotAvailableException.NO_POLLING
by Mark Addleman (JIRA)
Mark Addleman created TEIID-3499:
------------------------------------
Summary: IllegalStateException wihle using DataNotAvailableException.NO_POLLING
Key: TEIID-3499
URL: https://issues.jboss.org/browse/TEIID-3499
Project: Teiid
Issue Type: Feature Request
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)
8 years, 11 months
[JBoss JIRA] (TEIID-3475) Add a separate example module for embedded examples
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3475?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3475:
-------------------------------------
I am not sure why GUI launcher is important, so I am I have to say I am not in favor of it unless there is something that provides valuable. Here these examples are more like templates for someone to get a head start. I believe, we also getting off topic from original intent of the JIRA.
> 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)
8 years, 11 months
[JBoss JIRA] (TEIID-2469) Pre-Load Materialised Views
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2469?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2469:
---------------------------------------
We also have a design issue in that the vdb state is not truly complete until the all of the other life cycle listeners have run. The workaround for now is to hard code in the vdbrepository that the materializationmanager must be called last.
> Pre-Load Materialised Views
> ---------------------------
>
> Key: TEIID-2469
> URL: https://issues.jboss.org/browse/TEIID-2469
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Currently teiid does not load materialised views automatically. The request has to come for the materialised view or it has to be explicitly loaded. As materialised views are made with the purpose of preloading data, teiid should load the materialised views as default. There can be a tag or switch which will determine if the materialise views are to be preloaded or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-3498) missing message keys in function descriptions
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3498:
-------------------------------------
Summary: missing message keys in function descriptions
Key: TEIID-3498
URL: https://issues.jboss.org/browse/TEIID-3498
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
Function metadata contains missing an incorrect entries - such as seen in TestMMDatabaseMetadata.testGetFunctionColumns
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-2469) Pre-Load Materialised Views
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2469?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2469:
---------------------------------------
Added the initial implementation that ties internal mat views with the external logic. If the allow management property is used on an internal materialized view, then it will be pre-loaded and will have it's refresh done via the MaterializationManager - although this logic is weaker than what I would like and generally uses a fixed ttl, such that any modification of the ttl property at runtime won't be effective.
There appeared to be several issues with the MaterializationManager that this check in attempted to address:
1. how tasks accessed in the map was inconsistent, for example removal just based upon the task rather than looking up first by vdb key
2. the use of a timer should be avoided when possible, also it's possible to consolidate in embedded several asynch thread pools
3. there should be a way to execute a query asynchly, as having a thread waiting on future.get isn't necessary for just a refresh. however I only made this change for the internal case
4. the external logic didn't seem to keep rescheduling the next load in all cases - for example if the mat view is currently loading, then the task no longer repeats.
5. there was duplication in the executeQuery code between the two implementations
> Pre-Load Materialised Views
> ---------------------------
>
> Key: TEIID-2469
> URL: https://issues.jboss.org/browse/TEIID-2469
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Currently teiid does not load materialised views automatically. The request has to come for the materialised view or it has to be explicitly loaded. As materialised views are made with the purpose of preloading data, teiid should load the materialised views as default. There can be a tag or switch which will determine if the materialise views are to be preloaded or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-3496) update status table in ON_VDB_DROP_SCRIPT should point to correct name and schemaname
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3496?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3496.
-----------------------------------
Fix Version/s: 8.11
Resolution: Done
Merged the pull request.
> update status table in ON_VDB_DROP_SCRIPT should point to correct name and schemaname
> -------------------------------------------------------------------------------------
>
> Key: TEIID-3496
> URL: https://issues.jboss.org/browse/TEIID-3496
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 8.11
>
>
> This may be caused by miss spelling , in "teiid_rel:ON_VDB_DROP_SCRIPT" section, the name and schemaname should point to stockPricesMatView and StocksMatModel, but current looks
> ~~~
> <model name="StocksMatModel" type="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> CREATE view stockPricesMatView
> ...
> ) OPTIONS(
> ...
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'DELETE FROM Accounts.status WHERE Name=''stock'' AND schemaname = ''Stocks''',
> ~~~
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months