aboutsummaryrefslogtreecommitdiffstats
path: root/package.json
diff options
context:
space:
mode:
authorLibravatar Kristóf Marussy <kristof@marussy.com>2023-03-01 02:15:50 +0100
committerLibravatar Kristóf Marussy <kristof@marussy.com>2023-03-01 11:10:39 +0100
commitda5d898b3bad6f55efd6619f0abee0ec8aa1de4b (patch)
treed752bb975189a52aaaa5211e64dec42ea0b152fe /package.json
parentchore(deps): bump dependencies (diff)
downloadrefinery-da5d898b3bad6f55efd6619f0abee0ec8aa1de4b.tar.gz
refinery-da5d898b3bad6f55efd6619f0abee0ec8aa1de4b.tar.zst
refinery-da5d898b3bad6f55efd6619f0abee0ec8aa1de4b.zip
refactor: more direct access to VIATRA result set
Accessing VIATRA result sets through IQueryResultProvider requires a lot of indirection, allocations, and locking. We use reflection instead to have direct access to the underlying Indexer instead. Unfortunately, projection to arbitrary tuple masks (with wildcard entries in a tuple) is completely broken in VIATRA when RETE update propagation is delayed. While a new, ad-hoc projection indexer gets added to the RETE net immediately, it is not populated with the projection results until updates are flushed in the query engine. Therefore, when encountering an ad-hoc projection for the first time, the projection results will always be empty (thus usually out of date). While declaring the desired projections ahead of time would be a possible solution, for now, we completely remove ad-hoc projection support. If projections are needed on the ModelQuery level, we should create an API for declaring projections for each registered Dnf.
Diffstat (limited to 'package.json')
0 files changed, 0 insertions, 0 deletions