[KYUUBI #5687] Using session user as proxy user to execute statements at the server and group share level

[theoryxu]

🔍 Description

Issue References 🔗

This pull request fixes #5687

Describe Your Solution 🔧

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Types of changes 🔖

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪

Behavior Without This Pull Request ⚰️

Behavior With This Pull Request 🎉

Related Unit Tests

---

Checklists

📝 Author Self Checklist

• My code follows the style guidelines of this project
• I have performed a self-review
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

• Pull request title is okay.
• No license issues.
• Milestone correctly set?
• Test coverage is ok
• Assignees are selected.
• Minimum number of approvals
• No changes are requested

Be nice. Be informative.

For caution, the parameter set false as the default

[pan3793]

@theoryxu it would be nice if you could add a UT for this feature, to demonstrate the behavior differences with this feature enabled/disabled.

[theoryxu]

@theoryxu it would be nice if you could add a UT for this feature, to demonstrate the behavior differences with this feature enabled/disabled.

@pan3793 Thank you for your review.

I‘ll figure out how Kyuubi's UT framework works and add one for this.

By the way, Are there other flaws I should know about? I could fix it at once.

[pan3793]

@theoryxu I'm looking at the implementation in STS, which seems different, I suspect the behaviors are also different.