Hi all,
I have done some evaluation on the issue and opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=522208 to track this.
TL;DR: if my evaluation is correct, we kept the old behavior of the base index, but as a consequence changed the default behavior of queries evaluated with Rete.
Best regards,
-----
Ábel Hegedüs
IncQuery Labs Ltd.
On 2017. 08. 25. 11:30:57, Zoltán Ujhelyi <zoltan.ujhelyi@xxxxxxxxxxxxxxxx> wrote:
On the 23rd March we decided we should not change it: https://wiki.eclipse.org/VIATRA/DeveloperMeetingMinutes/Meeting20170323
This seems like a regression to me, especially considering the New and noteworthy also states the default semantics is the backwards compatible one: "For backward compatibility, the old behavior is used by default, but you can manually change this using the corresponding base index option as below. For new code we suggest to use this option to drop the dangling-free assumption, as it provides more consistent and intuitive results in a lot of cases; in a future VIATRA release this will be the new default.”
Zoli
-- Zoltán Ujhelyi
Eclipse Technologies Expert
IncQueryLabs Ltd.
> On 2017. Aug 25., at 11:26, Balázs Grill wrote:
>
> 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
> _______________________________________________
> viatra-dev mailing list
> viatra-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/viatra-dev
_______________________________________________
viatra-dev mailing list
viatra-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/viatra-dev
