Uh oh!
There was an error while loading. Please reload this page.
[SPARK-21492][SQL][Follow Up] Reimplement UnsafeExternalRowSorter in database style iterator - #26229
Closed
xuanyuanking wants to merge 1 commit into
Closed
[SPARK-21492][SQL][Follow Up] Reimplement UnsafeExternalRowSorter in database style iterator#26229xuanyuanking wants to merge 1 commit into
xuanyuanking wants to merge 1 commit into
Conversation
xuanyuanking
commented
Oct 23, 2019
MemberAuthor
cc @cloud-fan |
SparkQA
commented
Oct 23, 2019
Test build #112547 has finished for PR 26229 at commit
|
cloud-fan pushed a commit
that referenced
this pull request
Oct 24, 2019
…database style iterator ### What changes were proposed in this pull request? Reimplement the iterator in UnsafeExternalRowSorter in database style. This can be done by reusing the `RowIterator` in our code base. ### Why are the changes needed? During the job in #26164, after involving a var `isReleased` in `hasNext`, there's possible that `isReleased` is false when calling `hasNext`, but it becomes true before calling `next`. A safer way is using database-style iterator: `advanceNext` and `getRow`. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Existing UT. Closes#26229 from xuanyuanking/SPARK-21492-follow-up. Authored-by: Yuanjian Li <xyliyuanjian@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com> (cherry picked from commit 9e77d48) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
cloud-fan
commented
Oct 24, 2019
Contributor
thanks, merging to master/2.4! |
xuanyuanking
commented
Oct 24, 2019
MemberAuthor
Thanks Wenchen. |
| row.pointTo( | ||
| sortedIterator.getBaseObject(), | ||
| sortedIterator.getBaseOffset(), | ||
| sortedIterator.getRecordLength()); |
wangqia0309 pushed a commit
to bigo-sg/spark
that referenced
this pull request
Oct 31, 2019
…database style iterator ### What changes were proposed in this pull request? Reimplement the iterator in UnsafeExternalRowSorter in database style. This can be done by reusing the `RowIterator` in our code base. ### Why are the changes needed? During the job in apache#26164, after involving a var `isReleased` in `hasNext`, there's possible that `isReleased` is false when calling `hasNext`, but it becomes true before calling `next`. A safer way is using database-style iterator: `advanceNext` and `getRow`. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? Existing UT. Closesapache#26229 from xuanyuanking/SPARK-21492-follow-up. Authored-by: Yuanjian Li <xyliyuanjian@gmail.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com> (cherry picked from commit 9e77d48) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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?
Reimplement the iterator in UnsafeExternalRowSorter in database style. This can be done by reusing the
RowIteratorin our code base.Why are the changes needed?
During the job in #26164, after involving a var
isReleasedinhasNext, there's possible thatisReleasedis false when callinghasNext, but it becomes true before callingnext. A safer way is using database-style iterator:advanceNextandgetRow.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing UT.