Skip to content

Conversation

@beliefer
Copy link
Contributor

What changes were proposed in this pull request?

I checked all the config of Spark again. find some new commit not add version information.

Test.scala

Item name Since version JIRA ID Commit ID Note
spark.testing.skipValidateCores 3.1.0 SPARK-29154 474b1bb#diff-8b4ea8f3b0cc1e7ce7e943de1abbb165  

SQL

Item name Since version JIRA ID Commit ID Note
spark.sql.legacy.integerGroupingId 3.1.0 SPARK-30279 71c73d5#diff-9a6b543db706f1a90f790783d6930a13  

The two config only exists in branch master.

Why are the changes needed?

Supplement version information.

Does this PR introduce any user-facing change?

'No'.

How was this patch tested?

Jenkins test.

// on the host.
val SKIP_VALIDATE_CORES_TESTING =
ConfigBuilder("spark.testing.skipValidateCores")
.version("3.1.0")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

SPARK-29154, commit ID: 474b1bb#diff-8b4ea8f3b0cc1e7ce7e943de1abbb165

Copy link
Member

Choose a reason for hiding this comment

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

Do we need this? this is an internal testing config, not for users

Copy link
Contributor Author

@beliefer beliefer Apr 17, 2020

Choose a reason for hiding this comment

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

@srowen Thanks for your review. Based on my investigation. In the past, some internal configurations will be changed into public ones.
So it is possible for this configuration to become public in the future.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, we don't really need this strictly. It's just a good to know when we make it public later. These versions happened to be marked for all other configurations, and these look the only instances left. Should be fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks.

buildConf("spark.sql.legacy.integerGroupingId")
.internal()
.doc("When true, grouping_id() returns int values instead of long values.")
.version("3.1.0")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

SPARK-30279, commit ID: 71c73d5#diff-9a6b543db706f1a90f790783d6930a13

@beliefer
Copy link
Contributor Author

@HyukjinKwon We may tell all the committers to pay attention to the version information when adding configuration when submitting or reviewing.

@SparkQA
Copy link

SparkQA commented Apr 16, 2020

Test build #121366 has finished for PR 28233 at commit 1083964.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@beliefer
Copy link
Contributor Author

retest this please

@HyukjinKwon
Copy link
Member

@beliefer, it's strictly not a must-to-do to specify an added version for internal configurations. We don't really take care about the compatibility in these. It's just a good to know internally, and good to keep it consistent with other configurations.

But sure, cc @tgravescs and @maropu FYI.

@beliefer
Copy link
Contributor Author

@HyukjinKwon Thanks. It's true that we don't have to be strict. Let's keep it consistent with other configurations in style.

@SparkQA
Copy link

SparkQA commented Apr 17, 2020

Test build #121388 has finished for PR 28233 at commit 1083964.

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

@HyukjinKwon
Copy link
Member

Merged to master.

@maropu
Copy link
Member

maropu commented Apr 17, 2020

Yea, looks fine to me, too.

@beliefer beliefer deleted the sql-conf-version-legacy-integerGroupingId branch April 23, 2024 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants