Uh oh!
There was an error while loading. Please reload this page.
[SPARK-14721][SQL] Remove HiveContext (part 2) - #12585
Conversation
8e6e2b1 to
0e16190CompareSparkQA
commented
Apr 21, 2016
Test build #56593 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 21, 2016
Test build #56592 has finished for PR 12585 at commit
|
## What changes were proposed in this pull request? Just a rename so we can get rid of `HiveContext.scala`. Note that this will conflict with apache#12585. ## How was this patch tested? No change in functionality. Author: Andrew Or <andrew@databricks.com> Closesapache#12586 from andrewor14/rename-hc-object.
SparkQA
commented
Apr 22, 2016
Test build #56617 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 22, 2016
Test build #56628 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 22, 2016
Test build #56630 has finished for PR 12585 at commit
|
andrewor14
commented
Apr 22, 2016
Hm, seems that I'll need to fix the python thing in this patch. |
SparkQA
commented
Apr 22, 2016
Test build #56722 has finished for PR 12585 at commit
|
andrewor14
commented
Apr 23, 2016
retest this please |
SparkQA
commented
Apr 23, 2016
Test build #56756 has finished for PR 12585 at commit
|
rxin
commented
Apr 24, 2016
The changes look good to me. |
SparkQA
commented
Apr 25, 2016
Test build #2868 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 25, 2016
Test build #56907 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 25, 2016
Test build #2869 has finished for PR 12585 at commit
|
SparkQA
commented
Apr 25, 2016
Test build #2870 has finished for PR 12585 at commit
|
yhuai
commented
Apr 25, 2016
LGTM |
andrewor14
commented
Apr 25, 2016
Thanks merging into master. |
What changes were proposed in this pull request?
This removes the class
HiveContextitself along with all code usages associated with it. The bulk of the work was already done in #12485. This is mainly just code cleanup and actually removing the class.Note: A couple of things will break after this patch. These will be fixed separately.
How was this patch tested?
No change in functionality.