spark plan test looks at consistent naming vs actual node values #9182
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 Does This Do
Instead of looking at the hardcoded nodeId values, that are hashes of node
toStringmethod which can vary, we only check whether the nodeId naming captured by the instrumentation is consistent - so, whether value between plans that refer to the same node has the same id.This is done by remapping the ids to sequential
nodeId_Xvalues if they haven't been seen already, and assigning the value if it has been seen before.