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-34520][CORE] Remove unused SecurityManager references #31636

Closed
wants to merge 3 commits into from

Conversation

HyukjinKwon
Copy link
Member

What changes were proposed in this pull request?

This is kind of a followup of #24033 and #30945.
Many of references in SecurityManager were introduced from SPARK-1189, and related usages were removed later from #24033 and #30945. This PR proposes to remove them out.

Why are the changes needed?

For better readability of codes.

Does this PR introduce any user-facing change?

No, dev-only.

How was this patch tested?

Manually complied. GitHub Actions and Jenkins build should test it out as well.

@HyukjinKwon HyukjinKwon requested review from srowen and dongjoon-hyun and removed request for srowen February 24, 2021 12:06
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 tests pass and it's just removing unneeded references

@SparkQA
Copy link

SparkQA commented Feb 24, 2021

Test build #135423 has finished for PR 31636 at commit 4b6a452.

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

@dongjoon-hyun
Copy link
Member

+1 for the proposal. Looks correct.

@SparkQA
Copy link

SparkQA commented Feb 25, 2021

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40024/

@SparkQA
Copy link

SparkQA commented Feb 25, 2021

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40024/

@HyukjinKwon
Copy link
Member Author

Addressed comments and resolved the conflicts.

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

+1, LGTM (only one indentation comment)

@SparkQA
Copy link

SparkQA commented Feb 25, 2021

Test build #135444 has finished for PR 31636 at commit e504096.

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

@dongjoon-hyun
Copy link
Member

Merged to master. Thanks!

@dongjoon-hyun dongjoon-hyun deleted the SPARK-34520 branch February 25, 2021 04:38
@HyukjinKwon
Copy link
Member Author

Thank you @dongjoon-hyun!

@SparkQA
Copy link

SparkQA commented Feb 25, 2021

Test build #135446 has finished for PR 31636 at commit 9a3633a.

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

HyukjinKwon added a commit that referenced this pull request Mar 1, 2021
### What changes were proposed in this pull request?

This is a followup of #31636. There was one place missed in `GangliaSink`, and we should also remove `SecurityManager`.

### Why are the changes needed?

To make `GangliaSink` work.

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

No.

### How was this patch tested?

It was found in the internal it tests in the company I work for.

Closes #31688 from HyukjinKwon/SPARK-34520-followup.

Authored-by: HyukjinKwon <[email protected]>
Signed-off-by: HyukjinKwon <[email protected]>
@dongjoon-hyun
Copy link
Member

Unfortunately, I missed that this is a breaking change due to the following.

val sink = Utils.classForName[Sink](classPath)
- .getConstructor(
-   classOf[Properties], classOf[MetricRegistry], classOf[SecurityManager])
- .newInstance(kv._2, registry, securityMgr)
+ .getConstructor(classOf[Properties], classOf[MetricRegistry])
+ .newInstance(kv._2, registry)

@dongjoon-hyun
Copy link
Member

I'll make a PR.

@dongjoon-hyun
Copy link
Member

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.

4 participants