Retrieve Explanations Sequentially #57
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR?
Matching protocol changes in typedb/typedb-protocol#20, we now iteratively retrieve layers of the
Explanation
tree of aConceptMap
answer.ConceptMap.explanation()
does a round trip to the Grakn server and retrieves a list ofConceptMap
that explain how the given concept map was obtained. We also restrictExplanation
to only be obtainable fromConceptMap
, given that we have not implementedExplanation
on delete, count, etc. queries.What are the changes implemented in this PR?
ConceptMap
contains aqueryPattern
-- this is empty if reasoner is not triggered, and the new methodhasExplanation()
will returnfalse
hasExplanation()
is true, it is possible to send the ConceptMap back to the server viaTransaction
to obtain anExplanation
objectExplanation
object only contains a list ofConceptMap