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

[#4973] improvement(client-java/server): Clear CallerContext in Java Client and Server when call getFileLocation finally #4974

Merged
merged 1 commit into from
Sep 20, 2024

Conversation

xloya
Copy link
Collaborator

@xloya xloya commented Sep 20, 2024

What changes were proposed in this pull request?

Currently, after the client completes the getFileLocation request and the server completes the getFileLocation response, the Thread Local CallerContext is not cleaned up. This may cause the next request to incorrectly report the same information repeatedly when the thread is reused. We should eventually clean up the CallerContext.

Why are the changes needed?

Fix: #4973

How was this patch tested?

Add UTs.

@xloya xloya force-pushed the remove-caller-context-finally branch from 5f9854f to 2d46469 Compare September 20, 2024 09:16
@xloya xloya changed the title [#4973] improvement(client-java/server): Remove CallerContext in Java Client and Server [#4973] improvement(client-java/server): Clear CallerContext in Java Client and Server when call getFileLocation finally Sep 20, 2024
@xloya xloya self-assigned this Sep 20, 2024
@xloya xloya closed this Sep 20, 2024
@xloya xloya reopened this Sep 20, 2024
@jerryshao jerryshao merged commit 8aee4a3 into apache:main Sep 20, 2024
54 of 55 checks passed
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.

[Improvement] Clear CallerContext after the getFileLocation request and response
2 participants