[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4461:
-----------------------------------
Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17))
> Use date picker for LocalDate
> -----------------------------
>
> Key: DROOLS-4461
> URL: https://issues.redhat.com/browse/DROOLS-4461
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor
> Reporter: Toni Rikkola
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> We should use the date picker for LocalDate like we do for Date.
> h2. Acceptance test
> - Guided rule condition (/)
> - Guided rule action (/)
> - Guided rule template condition (/)
> - Guided rule template action (/)
> - Guided decision table simple condition (/)
> - Guided decision table BRL condition (/)
> - Guided decision table simple action (/)
> - Guided decision table BRL action (/)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4367:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 34-36 (from Aug 17))
> Tests in drools coverage are not really using the executable model
> ------------------------------------------------------------------
>
> Key: DROOLS-4367
> URL: https://issues.redhat.com/browse/DROOLS-4367
> Project: Drools
> Issue Type: Bug
> Reporter: Luca Molteni
> Assignee: Daniel Rosa
> Priority: Minor
>
> Such as
> https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d...
> Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5486) CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5486?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5486:
-----------------------------------
Sprint: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17))
> CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5486
> URL: https://issues.redhat.com/browse/DROOLS-5486
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.39.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> With the below test, standard-drl fires but executable-model doesn't.
> {code:java}
> @Test
> public void testAfterOnLongFields2() throws Exception {
> String str =
> "import " + StockTick.class.getCanonicalName() + ";\n" +
> "declare StockTick @timestamp(timeFieldAsLong) end\n" +
> "rule R when\n" +
> " $a : StockTick( company == \"DROO\" )\n" +
> " $b : StockTick( company == \"ACME\", $a.timeFieldAsLong after[5,8] timeFieldAsLong )\n" +
> "then\n" +
> " System.out.println(\"fired\");\n" +
> "end\n";
> KieSession ksession = getKieSession(getCepKieModuleModel(), str);
> SessionPseudoClock clock = ksession.getSessionClock();
>
> ReteDumper.dumpRete(ksession);
> ksession.insert( new StockTick( "ACME" ).setTimeField( 0 ) );
> ksession.insert( new StockTick( "DROO" ).setTimeField( 6 ) );
> assertEquals( 1, ksession.fireAllRules() );
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5608) Cannot use method chaining as source for facts
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5608?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5608:
-----------------------------------
Sprint: 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 34-36 (from Aug 17))
> Cannot use method chaining as source for facts
> ----------------------------------------------
>
> Key: DROOLS-5608
> URL: https://issues.redhat.com/browse/DROOLS-5608
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.42.0.Final
> Reporter: Ciprian Chiru
> Assignee: Luca Molteni
> Priority: Major
>
> Given the sample rule below:
> {code:java}
> import java.util.*;
> global java.util.Set controlSet;
> rule "will execute per each Measurement having ID color"
> no-loop
> when
> Measurement( id == "color", $colorVal : val )
> String() from Optional.of($colorVal).orElse("blah")
> then
> controlSet.add($colorVal);
> end{code}
>
> Compiling the resulting model fails with:
> {code:java}
> .../target/generated-sources/drools-model-compiler/main/java/rules/Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0.java:[24,129] cannot find symbol
> [ERROR] symbol: variable $colorVal
> [ERROR] location: class rules.Rules79f20b1c9ba841128eaf4b2dbb336819RuleMethods0{code}
> Can be reproduced with _7.43.0-SNAPSHOT_
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-4605) DMN alpha network
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4605?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4605:
-----------------------------------
Sprint: 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7) (was: 2020 Week 34-36 (from Aug 17))
> DMN alpha network
> -----------------
>
> Key: DROOLS-4605
> URL: https://issues.redhat.com/browse/DROOLS-4605
> Project: Drools
> Issue Type: Story
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Major
>
> *Motivation*: a DMN decision table can be evaluated faster than naive algorithm by translating it into a Rete/Phreak, but the current kie7 approach is suffering from performance bottleneck artificially induced by use of kie7 rule units, which provide more harm than benefit to perfomance (performance is actually worst for most "realistic" cases).
> *Goals*: a POC to understand what’s need to be done to support the alpha network compiler (wihout kie7 rule units) in DMN. We currently estimate it will take us 1 to 2 summer sprints and the output will be more epics to implement this feature.
> *Impact*: alpha network compiler code refactors for the better use of.
> One part of the POC was to hard-code the alpha network for a specific table ([DROOLS-4566]) the remained of the poc is to generalize the approach further to fully assess the impacts thanks to the poc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years