[Subscription] Suppress pull commit progress error when subscription is disabled - #18564
Merged
JackieTien97 merged 1 commit intoSep 2, 2026
Conversation
JackieTien97
approved these changes
Sep 2, 2026
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
When
subscription_enabled=falseon a DataNode,pullCommitProgressreturnsUNSUPPORTED_OPERATION(status code 300). The ConfigNode handler now treats this expected response as a silent no-op instead of emitting an error log. Other failures continue to be logged at error level.Tests
mvn spotless:apply -pl iotdb-core/confignodemvn -o compile -pl iotdb-core/confignode -DskipTests(Checkstyle and Spotless passed; the local JVM ran out of native memory duringjavac.)javaccompilation ofPullCommitProgressRPCHandler.javaagainst existing module artifacts passed.Checklist