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-12317][SQL] Support units (m,k,g) in SQLConf #10629

Closed
wants to merge 1 commit into from

Conversation

kevinyu98
Copy link
Contributor

This PR is continue from previous closed PR 10314.

In this PR, SHUFFLE_TARGET_POSTSHUFFLE_INPUT_SIZE will be taken memory string conventions as input.

For example, the user can now specify 10g for SHUFFLE_TARGET_POSTSHUFFLE_INPUT_SIZE in SQLConf file.

@marmbrus @srowen : Can you help review this code changes ? Thanks.

assert(sqlContext.conf.targetPostShuffleInputSize === -1)

// Test overflow exception
intercept[IllegalArgumentException] {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you indent the following properly?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise it will fail the style checker

@rxin
Copy link
Contributor

rxin commented Jan 7, 2016

Jenkins, ok to test.

@SparkQA
Copy link

SparkQA commented Jan 7, 2016

Test build #2349 has finished for PR 10629 at commit a37a05e.

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

@rxin
Copy link
Contributor

rxin commented Jan 8, 2016

I'm going to merge this and fix the indentation myself. Thanks.

@asfgit asfgit closed this in 5028a00 Jan 8, 2016
@kevinyu98
Copy link
Contributor Author

@rxin I am so sorry that I didn't reply earlier. The code passed the style check, I copied the code from the existing codes, and I thought the indentation 2 is fine. So I am not sure how to make changes. But appreciated your help. Next time, I will raise the questions more quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants