Revert changes to result entry naming for tooling compatibility #8
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.
Here is the requested set of changes to revert the result entry names to how they were in version 2.x to maintain compatibility with scripts that process them. The
time
(previouslyduration
) andresults
(previouslyresultCount
) are now back again, and the correspondingMax
andMin
entries have also been renamed. TheresultHash
column has been changed tohash
, as well, because it wasresultHash
to align it withresultCount
but that is gone now.The readme example now includes the full set of columns produced when running against a Comunica SPARQL endpoint that provides the
httpRequests
metadata, if you want to see exactly what it outputs. Hopefully this works better now with all the scripts. 🙂