| --- | --- |
| Bugzilla Link | 518783 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Jun 26, 2017 09:20 EDT |
| Modified | Feb 08, 2018 07:16 EDT |
| Version | 1.6.0 |
| Reporter | Denes Harmath |
Description
If a non-snapshot based match set provider is added to a ViatraQueryTest (with(IQueryBackendFactory)/with(QueryEvaluationHint)), and the scope is not explicitly given with on(...), the scope used in it is empty if there are no snapshot-based match set providers added before it, otherwise it is equal to the snapshot-based match set provider's scope registered directly before it. This behavior is error-prone.
If on() is not called, the non-snapshot based match set provider's scope should be always empty, and/or we should require a scope to be given to with() to make the empty scope explicit.
| --- | --- | | Bugzilla Link | 518783 | | Status | NEW | | Importance | P3 normal | | Reported | Jun 26, 2017 09:20 EDT | | Modified | Feb 08, 2018 07:16 EDT | | Version | 1.6.0 | | Reporter | Denes Harmath |
Description
If a non-snapshot based match set provider is added to a ViatraQueryTest (with(IQueryBackendFactory)/with(QueryEvaluationHint)), and the scope is not explicitly given with on(...), the scope used in it is empty if there are no snapshot-based match set providers added before it, otherwise it is equal to the snapshot-based match set provider's scope registered directly before it. This behavior is error-prone.
If on() is not called, the non-snapshot based match set provider's scope should be always empty, and/or we should require a scope to be given to with() to make the empty scope explicit.