[JBoss JIRA] (DROOLS-5187) DMN DT Analysis include `null` for gaps/overlaps calculation
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5187?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5187:
-----------------------------------
Description:
DMN DT Analysis include `null` for gaps/overlaps calculation where possible.
Implemented with considering a `null` value on a given a dimension:
* not "filling" Gaps on the other dimensions
* not causing Overlaps on the other dimensions
For example, in a table such as:
!screenshot-1.png|thumbnail!
Rule2 is not overlapping with Rule1, as they don't overlap on dimension/In1 not for a range not for a singularity value.
Rule2 is not "filling" any gaps either, as for Rule2 is not spanning for dimension/In1 in the range {{[-Inf, 0]}}, it cannot be a candidate to fill any gaps where in dimension/In2 {{>=0}}
Therefore the overall analysis for this table still is:
{code}
Gaps:
[ -Inf .. 0 ) ( 0 .. +Inf ]
[ 0 .. 0 ] [ 0 .. +Inf ]
( 0 .. +Inf ] [ -Inf .. 0 )
{code}
was:
DMN DT Analysis include `null` for gaps/overlaps calculation where possible.
Implemented with considering a `null` value on a given a dimension:
* not "filling" gaps on the other dimensions
* not causing Overlaps on the other dimensions
For example, in a table such as:
!screenshot-1.png|thumbnail!
Rule2 is not overlapping with Rule1, as they don't overlap on dimension/In1 not for a range not for a singularity value.
Rule2 is not "filling" any gaps either, as for Rule2 is not spanning for dimension/In1 in the range {{[-Inf, 0]}}, it cannot be a candidate to fill any gaps where in dimension/In2 {{>=0}}
Therefore the overall analysis for this table still is:
{code}
Gaps:
[ -Inf .. 0 ) ( 0 .. +Inf ]
[ 0 .. 0 ] [ 0 .. +Inf ]
( 0 .. +Inf ] [ -Inf .. 0 )
{code}
> DMN DT Analysis include `null` for gaps/overlaps calculation
> ------------------------------------------------------------
>
> Key: DROOLS-5187
> URL: https://issues.redhat.com/browse/DROOLS-5187
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png
>
>
> DMN DT Analysis include `null` for gaps/overlaps calculation where possible.
> Implemented with considering a `null` value on a given a dimension:
> * not "filling" Gaps on the other dimensions
> * not causing Overlaps on the other dimensions
> For example, in a table such as:
> !screenshot-1.png|thumbnail!
> Rule2 is not overlapping with Rule1, as they don't overlap on dimension/In1 not for a range not for a singularity value.
> Rule2 is not "filling" any gaps either, as for Rule2 is not spanning for dimension/In1 in the range {{[-Inf, 0]}}, it cannot be a candidate to fill any gaps where in dimension/In2 {{>=0}}
> Therefore the overall analysis for this table still is:
> {code}
> Gaps:
> [ -Inf .. 0 ) ( 0 .. +Inf ]
> [ 0 .. 0 ] [ 0 .. +Inf ]
> ( 0 .. +Inf ] [ -Inf .. 0 )
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4041) ManagementRealm does now show plain-text attribute in default read-resource output
by Michal Petrov (Jira)
[ https://issues.redhat.com/browse/WFCORE-4041?page=com.atlassian.jira.plug... ]
Michal Petrov commented on WFCORE-4041:
---------------------------------------
[~brian.stansberry], seems like this can be simply solved by letting the RAH check the nested attributes and add the defaults if they're not present (similar to WFCORE-2317). Though I suppose this might interfere with alternatives, I will have to check.
> ManagementRealm does now show plain-text attribute in default read-resource output
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4041
> URL: https://issues.redhat.com/browse/WFCORE-4041
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Justin Cook
> Assignee: Michal Petrov
> Priority: Major
>
> Currently running /subsystem=elytron/properties-realm=ManagementRealm:read-resource() results in the output:
> {code}
> {
> "outcome" => "success",
> "result" => {
> "groups-attribute" => "groups",
> "groups-properties" => {
> "path" => "mgmt-groups.properties",
> "relative-to" => "jboss.server.config.dir"
> },
> "users-properties" => {
> "path" => "mgmt-users.properties",
> "relative-to" => "jboss.server.config.dir",
> "digest-realm-name" => "ManagementRealm"
> }
> }
> }
> {code}
> which is missing the plain-text attribute
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5187) DMN DT Analysis include `null` for gaps/overlaps calculation
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5187?page=com.atlassian.jira.plug... ]
Matteo Mortari updated DROOLS-5187:
-----------------------------------
Description:
DMN DT Analysis include `null` for gaps/overlaps calculation where possible.
Implemented with considering a `null` value on a given a dimension:
* not "filling" gaps on the other dimensions
* not causing Overlaps on the other dimensions
For example, in a table such as:
!screenshot-1.png|thumbnail!
Rule2 is not overlapping with Rule1, as they don't overlap on dimension/In1 not for a range not for a singularity value.
Rule2 is not "filling" any gaps either, as for Rule2 is not spanning for dimension/In1 in the range {{[-Inf, 0]}}, it cannot be a candidate to fill any gaps where in dimension/In2 {{>=0}}
Therefore the overall analysis for this table still is:
{code}
Gaps:
[ -Inf .. 0 ) ( 0 .. +Inf ]
[ 0 .. 0 ] [ 0 .. +Inf ]
( 0 .. +Inf ] [ -Inf .. 0 )
{code}
was:DMN DT Analysis include `null` for gaps/overlaps calculation where possible
> DMN DT Analysis include `null` for gaps/overlaps calculation
> ------------------------------------------------------------
>
> Key: DROOLS-5187
> URL: https://issues.redhat.com/browse/DROOLS-5187
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png
>
>
> DMN DT Analysis include `null` for gaps/overlaps calculation where possible.
> Implemented with considering a `null` value on a given a dimension:
> * not "filling" gaps on the other dimensions
> * not causing Overlaps on the other dimensions
> For example, in a table such as:
> !screenshot-1.png|thumbnail!
> Rule2 is not overlapping with Rule1, as they don't overlap on dimension/In1 not for a range not for a singularity value.
> Rule2 is not "filling" any gaps either, as for Rule2 is not spanning for dimension/In1 in the range {{[-Inf, 0]}}, it cannot be a candidate to fill any gaps where in dimension/In2 {{>=0}}
> Therefore the overall analysis for this table still is:
> {code}
> Gaps:
> [ -Inf .. 0 ) ( 0 .. +Inf ]
> [ 0 .. 0 ] [ 0 .. +Inf ]
> ( 0 .. +Inf ] [ -Inf .. 0 )
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month