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

[MINOR] feat(spark-client): Support set accessId by another config dynamically #2250

Merged
merged 3 commits into from
Nov 18, 2024

Conversation

maobaolong
Copy link
Member

What changes were proposed in this pull request?

Support set accessId by another config dynamically.

Why are the changes needed?

Without this PR, we have to set accessId for each user belongs to spark.yarn.queue, after patch this feature, the spark.access.id set to the value of spark.yarn.queue, if we set spark.rss.access.id.provider.key=spark.yarn.queue

Does this PR introduce any user-facing change?

Introduce spark new config spark.rss.access.id.provider.key.

How was this patch tested?

Updated UT.

@codecov-commenter
Copy link

codecov-commenter commented Nov 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.88%. Comparing base (477bc30) to head (209ecee).
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2250      +/-   ##
============================================
+ Coverage     52.65%   52.88%   +0.23%     
- Complexity     3376     3552     +176     
============================================
  Files           514      532      +18     
  Lines         27565    29315    +1750     
  Branches       2582     2724     +142     
============================================
+ Hits          14513    15502     +989     
- Misses        12092    12824     +732     
- Partials        960      989      +29     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

github-actions bot commented Nov 16, 2024

Test Results

 2 956 files  ±0   2 956 suites  ±0   6h 28m 2s ⏱️ + 17m 40s
 1 092 tests ±0   1 090 ✅ ±0   2 💤 ±0  0 ❌ ±0 
13 685 runs  ±0  13 655 ✅ ±0  30 💤 ±0  0 ❌ ±0 

Results for commit 923a410. ± Comparison against base commit 4eebbd4.

♻️ This comment has been updated with latest results.

@@ -322,6 +322,9 @@ public class RssSparkConfig {

public static final ConfigEntry<String> RSS_ACCESS_ID =
createStringBuilder(new ConfigBuilder("spark.rss.access.id")).createWithDefault("");
public static final ConfigEntry<String> RSS_ACCESS_ID_PROVIDER_KEY =
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you use camel style?

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

I renamed to spark.rss.access.id.providerKey.

@jerqi
Copy link
Contributor

jerqi commented Nov 18, 2024

Could you add document, too?

@maobaolong
Copy link
Member Author

@jerqi Thanks for remind me, document added, PTAL.

@maobaolong
Copy link
Member Author

@jerqi Thanks for your review, merge it.

@maobaolong maobaolong merged commit b00b67c into apache:master Nov 18, 2024
43 checks passed
maobaolong added a commit to maobaolong/incubator-uniffle that referenced this pull request Nov 21, 2024
…namically (apache#2250)

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

Support set accessId by another config dynamically.

### Why are the changes needed?

Without this PR, we have to set accessId for each user belongs to `spark.yarn.queue`, after patch this feature, the `spark.access.id` set to the value of `spark.yarn.queue`, if we set `spark.rss.access.id.provider.key=spark.yarn.queue`

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

Introduce  spark new config `spark.rss.access.id.provider.key`.

### How was this patch tested?

Updated UT.

(cherry picked from commit b00b67c)
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