Skip to content

Conversation

bnouwt
Copy link
Collaborator

@bnouwt bnouwt commented Aug 12, 2025

Once the feature works, the matching process should be considerably faster and this test should succeed.

Once the feature works, the matching process should be considerably
faster and this test should succeed.
Not sure whether this will actually fly, because the matching process
should not be dependent on the ordering of the triple patterns in the
graph pattern and I am not sure whether this match flag is possible
without doing exactly that.
@bnouwt
Copy link
Collaborator Author

bnouwt commented Sep 26, 2025

Ran into an issue where depending on the order in which the triple patterns of a graph pattern are processed, different combi matches are produced. This should, of course, not happen, (i.e. the same graph patterns should always produce the same matches) so we have to see if we can find an improvement that does not have this unwanted property.

…mbinatory-explosion-but-also-prevents-combining-data-from-different-kbs-with-the-same-graph-pattern
Also, a few unit tests fail, which probably need to remove the matchflag
to function.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Additional match flag that prevents combinatory explosion but also prevents combining data from different KBs with the same graph pattern

1 participant