Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SPARK-4554][SQL] Set fair scheduler pool for JDBC client session in hive 13 #3416

Closed
wants to merge 2 commits into from
Closed

[SPARK-4554][SQL] Set fair scheduler pool for JDBC client session in hive 13 #3416

wants to merge 2 commits into from

Conversation

scwf
Copy link
Contributor

@scwf scwf commented Nov 22, 2014

No description provided.

@SparkQA
Copy link

SparkQA commented Nov 22, 2014

Test build #23743 has started for PR 3416 at commit bea4d87.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Nov 22, 2014

Test build #23743 has finished for PR 3416 at commit bea4d87.

  • This patch passes all 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/23743/
Test PASSed.

@marmbrus
Copy link
Contributor

marmbrus commented Dec 1, 2014

/cc @liancheng

Can you fix the merge conflict?

@scwf
Copy link
Contributor Author

scwf commented Dec 2, 2014

This have be fixed by @liancheng in #3506. to close this.

@scwf scwf closed this Dec 2, 2014
@liancheng
Copy link
Contributor

Yes, this is fixed in #3506 as a side effect, but I forgot to mention scheduler pool fix in that PR description.

@scwf scwf deleted the hive13-scheduling branch December 2, 2014 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@scwf @SparkQA @AmplabJenkins @marmbrus @liancheng