diff options
| author | Liang-Chi Hsieh <viirya@gmail.com> | 2016-03-10 10:04:56 -0800 |
|---|---|---|
| committer | Davies Liu <davies.liu@gmail.com> | 2016-03-10 10:04:56 -0800 |
| commit | d24801ad285ac3f2282fe20d1250a010673e2f96 (patch) | |
| tree | 50f17954052f4d70b79ea6eec890d04efa35f2ef /core | |
| parent | 74267beb3546d316c659499a9ff577437541f072 (diff) | |
| download | spark-d24801ad285ac3f2282fe20d1250a010673e2f96.tar.gz spark-d24801ad285ac3f2282fe20d1250a010673e2f96.tar.bz2 spark-d24801ad285ac3f2282fe20d1250a010673e2f96.zip | |
[SPARK-13636] [SQL] Directly consume UnsafeRow in wholestage codegen plans
JIRA: https://issues.apache.org/jira/browse/SPARK-13636
## What changes were proposed in this pull request?
As shown in the wholestage codegen verion of Sort operator, when Sort is top of Exchange (or other operator that produce UnsafeRow), we will create variables from UnsafeRow, than create another UnsafeRow using these variables. We should avoid the unnecessary unpack and pack variables from UnsafeRows.
## How was this patch tested?
All existing wholestage codegen tests should be passed.
Author: Liang-Chi Hsieh <viirya@gmail.com>
Closes #11484 from viirya/direct-consume-unsaferow.
Diffstat (limited to 'core')
0 files changed, 0 insertions, 0 deletions