Skip to content

Conversation

@scwf
Copy link
Contributor

@scwf scwf commented Oct 4, 2014

Do not use TestSQLContext in JavaHiveQLSuite, that may lead to two SparkContexts in one jvm and enable JavaHiveQLSuite

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@marmbrus
Copy link
Contributor

marmbrus commented Oct 4, 2014

ok to test

@SparkQA
Copy link

SparkQA commented Oct 4, 2014

QA tests have started for PR 2652 at commit be35c91.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Oct 4, 2014

QA tests have finished for PR 2652 at commit be35c91.

  • This patch passes unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/21298/Test PASSed.

@marmbrus
Copy link
Contributor

marmbrus commented Oct 6, 2014

Oh wow, good catch! I couldn't figure out why this wasn't working! Merged to master.

asfgit pushed a commit that referenced this pull request Oct 6, 2014
Do not use TestSQLContext in JavaHiveQLSuite, that may lead to two SparkContexts in one jvm and enable JavaHiveQLSuite

Author: scwf <[email protected]>

Closes #2652 from scwf/fix-JavaHiveQLSuite and squashes the following commits:

be35c91 [scwf] enable JavaHiveQLSuite

(cherry picked from commit 58f5361)
Signed-off-by: Michael Armbrust <[email protected]>
@asfgit asfgit closed this in 58f5361 Oct 6, 2014
@scwf scwf deleted the fix-JavaHiveQLSuite branch October 16, 2014 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants