diff options
author | David Navas <davidn@clearstorydata.com> | 2016-09-17 16:22:23 +0100 |
---|---|---|
committer | Sean Owen <sowen@cloudera.com> | 2016-09-17 16:22:23 +0100 |
commit | 9dbd4b864efacd09a8353d00c998be87f9eeacb2 (patch) | |
tree | f06c228df6d6582fc3466f0444b572cc1c875dfb /appveyor.yml | |
parent | 25cbbe6ca334140204e7035ab8b9d304da9b8a8a (diff) | |
download | spark-9dbd4b864efacd09a8353d00c998be87f9eeacb2.tar.gz spark-9dbd4b864efacd09a8353d00c998be87f9eeacb2.tar.bz2 spark-9dbd4b864efacd09a8353d00c998be87f9eeacb2.zip |
[SPARK-17529][CORE] Implement BitSet.clearUntil and use it during merge joins
## What changes were proposed in this pull request?
Add a clearUntil() method on BitSet (adapted from the pre-existing setUntil() method).
Use this method to clear the subset of the BitSet which needs to be used during merge joins.
## How was this patch tested?
dev/run-tests, as well as performance tests on skewed data as described in jira.
I expect there to be a small local performance hit using BitSet.clearUntil rather than BitSet.clear for normally shaped (unskewed) joins (additional read on the last long). This is expected to be de-minimis and was not specifically tested.
Author: David Navas <davidn@clearstorydata.com>
Closes #15084 from davidnavas/bitSet.
Diffstat (limited to 'appveyor.yml')
0 files changed, 0 insertions, 0 deletions