Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-252

VariableListeners for shadow variables that are triggered on other shadow variables should be triggered predictably in a smart order

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 6.3.0.CR2
    • None
    • optaplanner-core
    • None

    Description

      Currently the order is arbitrary.

      For example:
      genuine varA has a shadow varB
      genuine varA has a shadow varC
      shadow varB has a shadow varD
      shadow varC also has a shadow varD

      The order should be: varA, varB, varC, varD.
      The order should not be: varA, varB, varD, varC, varD again. That's wasteful.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-393 Broken TransportTimeToHubUpdatingVariableListener in Coach shuttle gathering

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-471 VariableListenerSupport.beforeVariableChanged() is severly slower (from CR1 to CR2) due to SortedMap usage

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-472 VariableListenerSupport.beforeVariableChanged() is severly slower (from CR1 to CR2) due to HashSet.add() usage

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-318 AnchorShadowVariable responsible for NullPointerException creating a ScoreDirector

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-482 NonUniqueNotificationVariableListener to forgo unique notification requirement in favor of performance gain

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-400 Detect cyclic shadow variables and fail fast

          • 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.
          • Resolved
          is duplicated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-388 way to specify order of CustomShadowVariable

          • 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.
          • Resolved
          is incorporated by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PLANNER-299 Vehicle Routing

          • 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.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-315 2 shadow vars updated by the same variable listener should not require 2 variable listener instances

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: