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-15297] [SQL] Fix Set -V Command #13081

Closed
wants to merge 3 commits into from

Conversation

gatorsmile
Copy link
Member

@gatorsmile gatorsmile commented May 12, 2016

What changes were proposed in this pull request?

The command SET -v always outputs the default values even if we set the parameter. This behavior is incorrect. Instead, if users override it, we should output the user-specified value.

In addition, the output schema of SET -v is wrong. We should use the column value instead of default for the parameter value.

This PR is to fix the above two issues.

How was this patch tested?

Added a test case.

@SparkQA
Copy link

SparkQA commented May 12, 2016

Test build #58506 has finished for PR 13081 at commit 6a23355.

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

@gatorsmile
Copy link
Member Author

@andrewor14 @yhuai @rxin Could you please review this PR? Thanks!

@SparkQA
Copy link

SparkQA commented May 15, 2016

Test build #58610 has finished for PR 13081 at commit ac371dc.

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

@gatorsmile
Copy link
Member Author

ping @hvanhovell @cloud-fan Do you have a bandwidth to review this simple fix? Thanks!

@gatorsmile
Copy link
Member Author

retest this please

@SparkQA
Copy link

SparkQA commented May 18, 2016

Test build #58817 has finished for PR 13081 at commit ac371dc.

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

asfgit pushed a commit that referenced this pull request May 19, 2016
#### What changes were proposed in this pull request?
The command `SET -v` always outputs the default values even if we set the parameter. This behavior is incorrect. Instead, if users override it, we should output the user-specified value.

In addition, the output schema of `SET -v` is wrong. We should use the column `value` instead of `default` for the parameter value.

This PR is to fix the above two issues.

#### How was this patch tested?
Added a test case.

Author: gatorsmile <gatorsmile@gmail.com>

Closes #13081 from gatorsmile/setVcommand.

(cherry picked from commit 9c2a376)
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
@asfgit asfgit closed this in 9c2a376 May 19, 2016
@cloud-fan
Copy link
Contributor

LGTM, merging to master and 2.0!

@gatorsmile
Copy link
Member Author

Thanks!

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