GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/7948
[SPARK-9611] [SQL] Fixes a few corner cases when we spill a
UnsafeFixedWidthAggregationMap
This PR has the following three small fixes.
1. UnsafeKVExternalSorter does not use 0 as the initialSize to create an
UnsafeInMemorySorter if its BytesToBytesMap is empty.
2. We will not not spill a InMemorySorter if it is empty.
3. We will not add a SpillReader to a SpillMerger if this SpillReader is
empty.
JIRA: https://issues.apache.org/jira/browse/SPARK-9611
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yhuai/spark unsafeEmptyMap
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/7948.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #7948
----
commit 34b6f76876f878c040fa1a706eed66d97b94d3ac
Author: Yin Huai <[email protected]>
Date: 2015-08-04T22:39:15Z
1. UnsafeKVExternalSorter does not use 0 as the initialSize to create an
UnsafeInMemorySorter if its BytesToBytesMap is empty.
2. Do not spill a InMemorySorter if it is empty.
3. Do not add spill to SpillMerger if this spill is empty.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
