[
https://issues.jboss.org/browse/JBRULES-3317?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3317:
-------------------------------------------
@Chris note added in the docs for 5.4.0.CR1, thanks for reporting
Planner should support a null planning value
--------------------------------------------
Key: JBRULES-3317
URL:
https://issues.jboss.org/browse/JBRULES-3317
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Fix For: 5.4.0.CR1
Several users on the user mailing list have run into this, especially for task assignment
use cases.
Example use case:
@PlanningEntity TaskAssignment assigns a Task to a @PlanningVariable Employee
There are so many Tasks, that's better to not assign some Tasks for now.
Current workaround:
Make a Employee representing NONE,
which is the only Employee instance that returns true on employee.isNone()
and the score rules are written to deal with that.
Technical difficulty to fix:
The @PlanningVariable(s) of a @PlanningEntity with planning value null are considered to
be "uninitialized".
Partial uninitialized solution detection is fundamental for repeated planning (including
real-time planning),
because the construction heuristics need to detect which parts of the solution to
intialize, but not everything because that takes too long.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira