[Red Hat JIRA] (DROOLS-4606) DMN alpha network POC
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4606?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4606:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> DMN alpha network POC
> ---------------------
>
> Key: DROOLS-4606
> URL: https://issues.redhat.com/browse/DROOLS-4606
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Luca Molteni
> Priority: Major
>
> Start refactoring work to support alpha network
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5877) Support MVEL BLiteral in the exec model
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5877?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5877:
-----------------------------------
Sprint: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> Support MVEL BLiteral in the exec model
> ---------------------------------------
>
> Key: DROOLS-5877
> URL: https://issues.redhat.com/browse/DROOLS-5877
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> It seems like it's already supported in the consequence
>
> [https://github.com/kiegroup/drools/blob/6408b5e1caa1e5c5fe94e45f82e1bedfb...]
>
>
> {code:java}
> package com.myspace.check20201202;
> //from row number: 1
> rule "Row 1 MatteoTable"
> dialect "mvel"
> when
> f1 : Person( age >= 18B )
> then
> f1.setMinor( false );
> end
> //from row number: 2
> rule "Row 2 MatteoTable"
> dialect "mvel"
> when
> f1 : Person( age < 18B )
> then
> f1.setMinor( true );
> end
> package com.myspace.check20201202;
> import java.math.BigDecimal;
> /**
> * This class was automatically generated by the data modeler tool.
> */
> public class Person implements java.io.Serializable {
> static final long serialVersionUID = 1L;
> private java.lang.String name;
> private BigDecimal age;
> private java.lang.Boolean minor;
> public Person() {
> }
> public java.lang.String getName() {
> return this.name;
> }
> public void setName(java.lang.String name) {
> this.name = name;
> }
> public java.lang.Boolean getMinor() {
> return this.minor;
> }
> public void setMinor(java.lang.Boolean minor) {
> this.minor = minor;
> }
> public java.math.BigDecimal getAge() {
> return this.age;
> }
> public void setAge(java.math.BigDecimal age) {
> this.age = age;
> }
> public Person(java.lang.String name, java.math.BigDecimal age,
> java.lang.Boolean minor) {
> this.name = name;
> this.age = age;
> this.minor = minor;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5729) Reorganize drools unit tests
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5729?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5729:
-----------------------------------
Sprint: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> Reorganize drools unit tests
> ----------------------------
>
> Key: DROOLS-5729
> URL: https://issues.redhat.com/browse/DROOLS-5729
> Project: Drools
> Issue Type: Story
> Components: core engine
> Affects Versions: 7.44.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network).
> Goals: Increase test coverage. More stable product.
> Impact: During this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat 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 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> 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
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5778) Rule evaluation optimization : alpha node range index additional enhancements
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5778?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5778:
-----------------------------------
Sprint: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> Rule evaluation optimization : alpha node range index additional enhancements
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5778
> URL: https://issues.redhat.com/browse/DROOLS-5778
> Project: Drools
> Issue Type: Story
> Components: core engine
> Affects Versions: 7.45.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Motivation: This Story follows up DROOLS-5631 to embrace additional enhancements related to alpha node range index.
> Goals: Better rule execution performance.
> Impact: Better rule execution performance. It might have slight overhead during rule build time.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5876) [Test Scenario Editor] Display actual test results instead of a generic message
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5876?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5876:
-----------------------------------
Sprint: 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 52-03 (from Dec 21))
> [Test Scenario Editor] Display actual test results instead of a generic message
> -------------------------------------------------------------------------------
>
> Key: DROOLS-5876
> URL: https://issues.redhat.com/browse/DROOLS-5876
> Project: Drools
> Issue Type: Enhancement
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
>
> In the second row, in the attached test scenario execution result, it gives an error on the List(3) value.
> When I hover over it, I don’t get to see the values of the list, generated by the test scenario, but only this generic message:
> "Error message: Impossible to find elements in the collection to satisfy the conditions"
> It would be handy to see, as, with single values, the list of the actual values generated so that I can compare them with my list of expected values. Now, the user doesn’t have a clue where to look.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5282) Client side FEEL
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5282?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5282:
-----------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 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), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 16-18 (from Apr 13), 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), 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21))
> Client side FEEL
> ----------------
>
> Key: DROOLS-5282
> URL: https://issues.redhat.com/browse/DROOLS-5282
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Make kie-dmn-feel usable in the client side.
> Notes:
> * FEEL functions use reflection, but many if not all of them can be hard coded
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months