[SPARK-22725][SQL] Add failing test for select with a splatted stream #19917
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 changes were proposed in this pull request?
Add additional test. I plan to file an issue in SPARK Jira soon detailing this change. It seems like there is an assumption in
.select
about some behavior that's not guaranteed bySeq
but does exist in aList
, because replacingStream
withSeq
in the test causes it to pass. Possibly this is due to Seq#map being lazy whereas List#map is eager.How was this patch tested?
Additional test.