| [viatra-dev] Change in default behavior of Rete engine regarding dangling edges between 1.5.3 and 1.6.0 |
|
Hi All, It seems that there is a change in the default (without any hint or base index options) behavior of the Viatra with RETE engine is changed. In 1.5 branch a ReteHintOption called checkScopeBoundaries was used to determine
whether the scope of cross-references shall be enforced. This option had a default value true, meaning proxies were considered as non-existing. The upper option is deprecated and ignored in 1.6, and no scope boundary enforcement is done by the RETE. A similar option is added to the base index (dangling free assumption), also with true default value, but with opposite
meaning. The true value means that scope boundaries are assumed and no check is necessary. This is the opposite semantics of the default settings in 1.5. I don’t remember what was the decision regarding the default behavior of dangling edges around 1.5.0. It was intentional to change
it again for 1.6.0? Regards Balázs Grill |