January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4932) DMN DT Analysis skip gap for unconstrained string

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4932?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4932: ----------------------------------- Attachment: screenshot-2.png > DMN DT Analysis skip gap for unconstrained string > ------------------------------------------------- > > Key: DROOLS-4932 > URL: https://issues.redhat.com/browse/DROOLS-4932 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4932) DMN DT Analysis skip gap for unconstrained string

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4932?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4932: ----------------------------------- Description: For a Decision Table such as: !screenshot-1.png|thumbnail! it does not make sense to compute Gap analysis because of the unconstrained string in the first column. However, DT static analysis still make sense for a table such as: !screenshot-2.png|thumbnail! where, while excluding gap analysis, still make sense to compute overlap, masked, misleading, etc. > DMN DT Analysis skip gap for unconstrained string > ------------------------------------------------- > > Key: DROOLS-4932 > URL: https://issues.redhat.com/browse/DROOLS-4932 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > For a Decision Table such as: > !screenshot-1.png|thumbnail! > it does not make sense to compute Gap analysis because of the unconstrained string in the first column. > However, DT static analysis still make sense for a table such as: > !screenshot-2.png|thumbnail! > where, while excluding gap analysis, still make sense to compute overlap, masked, misleading, etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4932) DMN DT Analysis skip gap for unconstrained string

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4932: -------------------------------------- Summary: DMN DT Analysis skip gap for unconstrained string Key: DROOLS-4932 URL: https://issues.redhat.com/browse/DROOLS-4932 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: screenshot-1.png, screenshot-2.png -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4932) DMN DT Analysis skip gap for unconstrained string

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4932?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4932: ----------------------------------- Attachment: screenshot-1.png > DMN DT Analysis skip gap for unconstrained string > ------------------------------------------------- > > Key: DROOLS-4932 > URL: https://issues.redhat.com/browse/DROOLS-4932 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4925) forall pattern with date constraint fail to match

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4925?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4925. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/0e180cef1870f87ed655215a88b9357... > forall pattern with date constraint fail to match > ------------------------------------------------- > > Key: DROOLS-4925 > URL: https://issues.redhat.com/browse/DROOLS-4925 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.29.0.Final, 7.30.0.Final, 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: forall-date-constraint.tgz, network.png > > > As of Drools 7.29.0.Final, {{forall}} patterns containing equality constraints on dates won't match as expected. > For instance, given the following drl > {noformat} > declare Fact > d : java.util.Date > end > > rule "forall with date" > when > forall(Fact(d == "01-Jan-2020")) > then > end > {noformat} > and the following working memory: > {noformat} > Fact( d=Wed Jan 01 00:00:00 CET 2020 ) > Fact( d=Wed Jan 01 00:00:00 CET 2020 ) > Fact( d=Wed Jan 01 00:00:00 CET 2020 ) > {noformat} > Drools <= 7.28.0.Final will fire 1 rule, whereas Drools >= 7.29.0.Final will fire 0 rules. > This is probably due to the fact that the rewriting implemented in [DROOLS-4632] fails to negate the constraint on the date, as visible in the attached picture of the network. > I am wondering whether there would be an equivalent problem with any constraint on dates (e.g., >=, <=, ...)? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-3339?page=com.atlassian.jira.plug... ] Daniele Zonca reassigned DROOLS-3339: ------------------------------------- Assignee: Gabriele Cardosi (was: Lance Leverich) > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.redhat.com/browse/DROOLS-3339 > Project: Drools > Issue Type: Feature Request > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: Michael McCune > Assignee: Gabriele Cardosi > Priority: Critical > Labels: PMMLRefactor > > Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12960) Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-12960?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFLY-12960: --------------------------------- Assignee: Ronald Sigal (was: Alessio Soldano) > Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions > -------------------------------------------------------------------------------- > > Key: WFLY-12960 > URL: https://issues.redhat.com/browse/WFLY-12960 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 19.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Ronald Sigal > Priority: Critical > > The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the configuration of the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. > We are already testing this in the integration tests, but it is good to test this closer to the source as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12960) Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-12960?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-12960: ------------------------------ Issue Type: Bug (was: Task) > Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions > -------------------------------------------------------------------------------- > > Key: WFLY-12960 > URL: https://issues.redhat.com/browse/WFLY-12960 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 19.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Critical > > The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the configuration of the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. > We are already testing this in the integration tests, but it is good to test this closer to the source as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12960) Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-12960?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-12960: ------------------------------ Description: The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the configuration of the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. We are already testing this in the integration tests, but it is good to test this closer to the source as well was:The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. > Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions > -------------------------------------------------------------------------------- > > Key: WFLY-12960 > URL: https://issues.redhat.com/browse/WFLY-12960 > Project: WildFly > Issue Type: Task > Components: REST > Affects Versions: 19.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Alessio Soldano > Priority: Critical > > The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the configuration of the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. > We are already testing this in the integration tests, but it is good to test this closer to the source as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12960) Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions

by Kabir Khan (Jira)

Kabir Khan created WFLY-12960: --------------------------------- Summary: Convert JaxrsSubsystemTestCase, and JaxrsTransformersTestCase to use expressions Key: WFLY-12960 URL: https://issues.redhat.com/browse/WFLY-12960 Project: WildFly Issue Type: Task Components: REST Affects Versions: 19.0.0.Beta1 Reporter: Kabir Khan Assignee: Alessio Soldano The comments leading up to https://github.com/wildfly/wildfly/pull/12835#issuecomment-574069027 made me realise that we are not using expressions in the subsystem tests. I don't think that needs to block the PR, but it should be changed for WildFly 19.0.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020