Pipe: use session context in legacy receiver loaders#18111
Merged
jt2594838 merged 3 commits intoJul 10, 2026
Conversation
jt2594838
approved these changes
Jul 7, 2026
| private SessionInfo getCurrentSessionInfo() { | ||
| final SessionManager sessionManager = SessionManager.getInstance(); | ||
| if (!sessionManager.checkLogin(sessionManager.getCurrSession())) { | ||
| throw new PipeException("Legacy pipe receiver requires a logged-in session."); |
Collaborator
Author
There was a problem hiding this comment.
Fixed, thanks. Moved the message into DataNodePipeMessages for both en and zh locales.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Legacy receiver session context
Legacy pipe receiver loading now uses the session context supplied by the RPC request path. The loader API accepts this context explicitly so deletion and tsfile loading follow the same request context.
Loader behavior
TsFile loading now follows the configured auto-create setting. The legacy receiver no longer performs database registration during handshake.
Tests
git diff --checkThis PR has:
Key changed/added classes (or packages if there are too many classes) in this PR