[Red Hat JIRA] (DROOLS-5917) Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5917?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5917:
---------------------------------
Priority: Minor (was: Major)
> Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5917
> URL: https://issues.redhat.com/browse/DROOLS-5917
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Minor
>
> It should be possible to put the actual constraints in comments in a generated ANC by leveraging the `PredicateInformation` class used in the executable model to give better error messages.
> In the compiled alpha network, instead of
> private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=Constraint for '0066e054-7241-4ccd-886d-ab6d7e08a99e' (index: null)]
> we should have
> private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=x == true" (index: null)]
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5917) Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5917?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5917:
---------------------------------
Issue Type: Enhancement (was: Bug)
> Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5917
> URL: https://issues.redhat.com/browse/DROOLS-5917
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> It should be possible to put the actual constraints in comments in a generated ANC by leveraging the `PredicateInformation` class used in the executable model to give better error messages.
> In the compiled alpha network, instead of
> private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=Constraint for '0066e054-7241-4ccd-886d-ab6d7e08a99e' (index: null)]
> we should have
> private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=x == true" (index: null)]
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5984:
---------------------------------
Issue Type: Enhancement (was: Feature Request)
> DMN Alpha Network - Range Indexing
> ----------------------------------
>
> Key: DROOLS-5984
> URL: https://issues.redhat.com/browse/DROOLS-5984
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Minor
>
> 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).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5984:
---------------------------------
Issue Type: Feature Request (was: Bug)
> DMN Alpha Network - Range Indexing
> ----------------------------------
>
> Key: DROOLS-5984
> URL: https://issues.redhat.com/browse/DROOLS-5984
> Project: Drools
> Issue Type: Feature Request
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Minor
>
> 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).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5984:
---------------------------------
Priority: Minor (was: Major)
> DMN Alpha Network - Range Indexing
> ----------------------------------
>
> Key: DROOLS-5984
> URL: https://issues.redhat.com/browse/DROOLS-5984
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Minor
>
> 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).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5990) DMN Alpha Network - Avoid In Memory Compilation
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5990?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5990:
---------------------------------
Description:
Using Alpha Network in DMN, currently che classes are generated and compiled in memory.
There should be a way to avoid InMemory compilation so that we can plug the DMN Alpha Network in with the maven plugin and therefore generate a kjar without using the inmemory compiler
was:
Using Alpha Network in DMN, each cell in a decision table can have multiple feel tests, but currently only the first is evaluated.
Support multi tests
> DMN Alpha Network - Avoid In Memory Compilation
> ------------------------------------------------
>
> Key: DROOLS-5990
> URL: https://issues.redhat.com/browse/DROOLS-5990
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Using Alpha Network in DMN, currently che classes are generated and compiled in memory.
> There should be a way to avoid InMemory compilation so that we can plug the DMN Alpha Network in with the maven plugin and therefore generate a kjar without using the inmemory compiler
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5990) DMN Alpha Network - Avoid In Memory Compilation
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5990:
------------------------------------
Summary: DMN Alpha Network - Avoid In Memory Compilation
Key: DROOLS-5990
URL: https://issues.redhat.com/browse/DROOLS-5990
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Luca Molteni
Assignee: Luca Molteni
Using Alpha Network in DMN, each cell in a decision table can have multiple feel tests, but currently only the first is evaluated.
Support multi tests
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years
[Red Hat JIRA] (DROOLS-5989) DMN Alpha Network - Support multiple Unary Tests for each Decision Table cell
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5989?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5989:
---------------------------------
Description:
Using Alpha Network in DMN, each cell in a decision table can have multiple feel tests, but currently only the first is evaluated.
Support multi tests
was:
Using Alpha Network in DMN, Feel test classes instantiated lazily the first time they're called and set to a static field.
That might generate some problem while evaluating decision tables with more than one thread.
> DMN Alpha Network - Support multiple Unary Tests for each Decision Table cell
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5989
> URL: https://issues.redhat.com/browse/DROOLS-5989
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Using Alpha Network in DMN, each cell in a decision table can have multiple feel tests, but currently only the first is evaluated.
> Support multi tests
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years