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

Selectors should support cacheType SOLVER with DroolsScoreDirector and IncrementalScoreDirector too: reuse multi-threading id technology to migrate the selector cache to the new solution clone

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Optional Optional
    • Future
    • None
    • optaplanner-core

      Selector cacheType solver doesn't work because between phases, the bestSolution is set as the workingSolution and entities get cloned. Therefor the cached moves are pointing to the old entities which haven't been inserted into the new Drools Expert working memory.

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

                Created:
                Updated: