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

NotNode proceeds with unmatched facts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 7.59.0.Final
    • core engine
    • None
    • 2021 Week 37-39 (from Sep 13), 2021 Week 40-42 (from Oct 4)
    • NEW
    • NEW

      A rule like this:

      rule R1
        when
          Cheese($type : type)
          not( Person( likes == $type, salary == null ) )
      
      • insert Cheese
      • Insert multiple Persons which don't match the rule (salary == null)
      • Update one Person with non-related property Note:This fact has to be a "blocker" in rightTuple in NotNode
      • Update the same Person to match the not (salary == 1000)
      • Still 2 Persons don't match the condition so the rule should not fire. — However, the rule fires

              mfusco@redhat.com Mario Fusco
              rhn-support-tkobayas Toshiya Kobayashi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: