Skip to content

Conversation

@cloud-fan
Copy link
Contributor

What changes were proposed in this pull request?

add .enabled postfix to spark.sql.analyzer.failAmbiguousSelfJoin.

Why are the changes needed?

to follow the existing naming style

Does this PR introduce any user-facing change?

no

How was this patch tested?

not needed

@cloud-fan
Copy link
Contributor Author

cc @gatorsmile

Copy link
Member

@srowen srowen left a comment

Choose a reason for hiding this comment

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

Seems fine if this was never released yet as a config that people use already.

@cloud-fan
Copy link
Contributor Author

yea this config is new in 3.0

@dongjoon-hyun dongjoon-hyun changed the title [SQL][minor] refine config name spark.sql.analyzer.failAmbiguousSelfJoin.enabled [MINOR][SQL] refine config name spark.sql.analyzer.failAmbiguousSelfJoin.enabled Nov 27, 2019

val FAIL_AMBIGUOUS_SELF_JOIN =
buildConf("spark.sql.analyzer.failAmbiguousSelfJoin")
buildConf("spark.sql.analyzer.failAmbiguousSelfJoin.enabled")
Copy link
Member

Choose a reason for hiding this comment

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

Could you update docs/sql-migration-guide.md, too? There is an instance referring this.

To restore the behavior before Spark 3.0, you can set spark.sql.analyzer.failAmbiguousSelfJoin to false.

.booleanConf
.createWithDefault(true)

val FAIL_AMBIGUOUS_SELF_JOIN =
Copy link
Member

@dongjoon-hyun dongjoon-hyun Nov 27, 2019

Choose a reason for hiding this comment

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

Maybe, FAIL_AMBIGUOUS_SELF_JOIN -> FAIL_AMBIGUOUS_SELF_JOIN_ENABLED?
It seems that we are using _ENABLED pattern for .enabled conf sometime.

@dongjoon-hyun dongjoon-hyun changed the title [MINOR][SQL] refine config name spark.sql.analyzer.failAmbiguousSelfJoin.enabled [MINOR][SQL] Rename config name to spark.sql.analyzer.failAmbiguousSelfJoin.enabled Nov 27, 2019
@SparkQA
Copy link

SparkQA commented Nov 27, 2019

Test build #114539 has finished for PR 26694 at commit 1b046e5.

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

@SparkQA
Copy link

SparkQA commented Dec 2, 2019

Test build #114715 has finished for PR 26694 at commit da05dce.

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

@cloud-fan
Copy link
Contributor Author

merging to master!

@cloud-fan cloud-fan closed this in e271664 Dec 2, 2019
@dongjoon-hyun
Copy link
Member

Thank you for update.
+1, late LGTM!

attilapiros pushed a commit to attilapiros/spark that referenced this pull request Dec 6, 2019
…lfJoin.enabled

### What changes were proposed in this pull request?

add `.enabled` postfix to `spark.sql.analyzer.failAmbiguousSelfJoin`.

### Why are the changes needed?

to follow the existing naming style

### Does this PR introduce any user-facing change?

no

### How was this patch tested?

not needed

Closes apache#26694 from cloud-fan/conf.

Authored-by: Wenchen Fan <wenchen@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
rshkv pushed a commit to palantir/spark that referenced this pull request Jan 28, 2021
…lfJoin.enabled

add `.enabled` postfix to `spark.sql.analyzer.failAmbiguousSelfJoin`.

to follow the existing naming style

no

not needed

Closes apache#26694 from cloud-fan/conf.

Authored-by: Wenchen Fan <wenchen@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants