Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-4896

Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 7.14.0.Final, 7.26.0.Final, 7.31.0.Final
    • core engine
    • 2020 Week 01-03 (from Dec 30)
    • Hide

      run attached reproducer by mvn clean test.

      Show
      run attached reproducer by mvn clean test.
    • NEW
    • NEW

    Description

      Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED".

      The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13).

      rule "rule1_BigDecimal"
    agenda-group "BigDecimal"
    when  
        accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal))
        accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2))
     
        $minFact: Fact( bdVal == new BigDecimal($minVal.intValue()))
        $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue()))
    then
    ...
 end

      But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work.
      i.e. rule fires one more time than expected even though there is only one fact at the last iteration.

      This does not happen at least with Long type.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1195 Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-4898 Accumulates: min does not work after retracting fact.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mfusco@redhat.com Mario Fusco
              rhn-support-hmiura Hiroko Miura
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: