[
https://issues.redhat.com/browse/DROOLS-5985?page=com.atlassian.jira.plug...
]
Luca Molteni updated DROOLS-5985:
---------------------------------
Description:
When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which
the first results of the output is returned.
Support different Hit Policies
was:
Currently alpha range index is not enabled probably because
AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for
"Application Risk Score" in DMNDecisionTableAlphaSupportingTest (=
ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false.
Also we would need to change range index threshold to test easier).
DMN Alpha Network - Support different Hit Policies
--------------------------------------------------
Key: DROOLS-5985
URL:
https://issues.redhat.com/browse/DROOLS-5985
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Luca Molteni
Assignee: Luca Molteni
Priority: Major
When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which
the first results of the output is returned.
Support different Hit Policies
--
This message was sent by Atlassian Jira
(v8.13.1#813001)