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.

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

[SPARK-19550][BUILD][FOLLOW-UP] Remove MaxPermSize for sql module #20268

Closed
wants to merge 1 commit into from
Closed

[SPARK-19550][BUILD][FOLLOW-UP] Remove MaxPermSize for sql module #20268

wants to merge 1 commit into from

Conversation

wangyum
Copy link
Member

@wangyum wangyum commented Jan 15, 2018

What changes were proposed in this pull request?

Remove MaxPermSize for sql module

How was this patch tested?

Manually tested.

@SparkQA
Copy link

SparkQA commented Jan 15, 2018

Test build #86129 has finished for PR 20268 at commit 6770835.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@wangyum
Copy link
Member Author

wangyum commented Jan 15, 2018

retest this please

@SparkQA
Copy link

SparkQA commented Jan 15, 2018

Test build #86131 has finished for PR 20268 at commit 6770835.

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

@srowen
Copy link
Member

srowen commented Jan 15, 2018

Merged to master/2.3

@asfgit asfgit closed this in a38c887 Jan 15, 2018
asfgit pushed a commit that referenced this pull request Jan 15, 2018
## What changes were proposed in this pull request?

Remove `MaxPermSize` for `sql` module

## How was this patch tested?

Manually tested.

Author: Yuming Wang <[email protected]>

Closes #20268 from wangyum/SPARK-19550-MaxPermSize.

(cherry picked from commit a38c887)
Signed-off-by: Sean Owen <[email protected]>
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.

3 participants