Bug 980775 - Queries using temporal operators do not return results
Summary: Queries using temporal operators do not return results
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER4
: 6.0.0
Assignee: Edson Tirelli
QA Contact: Tomas David
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-03 08:26 UTC by Marek Winkler
Modified: 2014-08-06 20:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:16:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Marek Winkler 2013-07-03 08:26:16 UTC 
Description of problem:

Queries using temporal queries return empty QueryResults, despite adding KieSession.fireAllRules() as required by phreak.

Please see pull request with the reproducer (CepQueryTest) for more details.


Version-Release number of selected component (if applicable):

Drools 6.0.0-SNAPSHOT
Drools 6.0.0.Beta4

This worked in 6.0.0.Beta3, marking as regression.


How reproducible:

Run the CepQueryTest (currently @Ignored) in drools-compiler integration tests.


Actual results:

Empty QueryResults are returned.


Expected results:

One event is returned in the query result.


Additional info:

The test uses two entry points but the problem is not related to them.
Comment 1 Marek Winkler 2013-07-03 08:30:08 UTC 
Pull request containing the reproducer: https://github.com/droolsjbpm/drools/pull/219
Comment 2 Marek Winkler 2013-09-06 18:31:31 UTC 
I have found this problem persists with ER2. Strangely, the query returns results when EventProcessingMode is set to CLOUD.
Comment 3 Edson Tirelli 2013-09-25 20:10:59 UTC 
Fixed master:

http://github.com/droolsjbpm/drools/commit/86be1a8eb

Fixed 6.0.x:

http://github.com/droolsjbpm/drools/commit/3ab6ee402
Comment 7 Tomas David 2013-10-16 09:37:28 UTC 
Verified on BRMS 6.0.0.ER4.

Queries using temporal operators now return results, but new problem has appeared (Bug 1019708).
Note You need to log in before you can comment on or make changes to this bug.