December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5910) Enable range index for JoinNode

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5910?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5910: ----------------------------------- Sprint: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 49-51 (from Nov 30)) > Enable range index for JoinNode > ------------------------------- > > Key: DROOLS-5910 > URL: https://issues.redhat.com/browse/DROOLS-5910 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Currently, BetaNode range index works only for NotNode and ExistsNode. Inequality constraints in JoinNode (e.g. $p2 : Person( age > $p1.age )) are not indexed in both standard-drl and exec-model. > https://github.com/kiegroup/drools/blob/master/drools-core/src/main/java/... > * Enable range index for JoinNode > * Fix issues based on failed tests > ** Type coercion > ** executable-model specific errors > ** maybe more > * Add more tests for join > * Add benchmark to confirm the effect -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5890) DMN DT Analysis 2NF detection edge-case

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5890?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5890: ----------------------------------- Sprint: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 49-51 (from Nov 30)) > DMN DT Analysis 2NF detection edge-case > --------------------------------------- > > Key: DROOLS-5890 > URL: https://issues.redhat.com/browse/DROOLS-5890 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > Detect edge case of 2NF violation such as > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5883) GDT editor generates wrong DRL if operator 'contains' is used with string literal containing space

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5883?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5883: ----------------------------------- Sprint: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 49-51 (from Nov 30)) > GDT editor generates wrong DRL if operator 'contains' is used with string literal containing space > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-5883 > URL: https://issues.redhat.com/browse/DROOLS-5883 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.47.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: guided_decision_table, support > > Guided Decision Table editor generate wrong DRL when using 'contains' operator with a string literal containing space., which causes evaluation/build error like. > [KBase: defaultKieBase]: [ERR 102] Line 7:45 mismatched input ')' in rule "Row 1 rule2" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[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) (was: 2020 Week 49-51 (from Nov 30)) > 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 (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[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) (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)) > 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 (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[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) (was: 2020 Week 34-36 (from Aug 17), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30)) > 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)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1257) Get list of SM image shas installed on the cluster

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1257?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1257. ---------------------------------- Resolution: Done Added https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/-/blob/master... > Get list of SM image shas installed on the cluster > -------------------------------------------------- > > Key: SWSQE-1257 > URL: https://issues.redhat.com/browse/SWSQE-1257 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When installing SM on cluster, different catalog sources might be used and it's easy to do a mistake. We need something which will list actually installed images so we can easily compare that we are testing expected payload. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5858) Investigate OptaPlanner's Bavet algorithm and compare it with Phreak

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5858?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5858: ----------------------------------- Sprint: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 49-51 (from Nov 30)) > Investigate OptaPlanner's Bavet algorithm and compare it with Phreak > -------------------------------------------------------------------- > > Key: DROOLS-5858 > URL: https://issues.redhat.com/browse/DROOLS-5858 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5853) Rule relationship analysis graph : convert model into graph

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5853?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5853: ----------------------------------- Sprint: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21) (was: 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30)) > Rule relationship analysis graph : convert model into graph > ----------------------------------------------------------- > > Key: DROOLS-5853 > URL: https://issues.redhat.com/browse/DROOLS-5853 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.46.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Convert model into navigable graph which is the basis of visualization (regardless of visualization methods). > See https://github.com/mariofusco/drools-impact-analysis -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[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) (was: 2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9), 2020 Week 49-51 (from Nov 30)) > 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 (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2020