Fix pipe tree database creation on receiver#17991
Open
Caideyipi wants to merge 1 commit into
Open
Conversation
52cf2da to
c5ed6e9
Compare
jt2594838
approved these changes
Jun 18, 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
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.
Supersedes #17986. That PR was accidentally marked as merged while
apache/masterwas force-restored; GitHub does not allow reopening a pull request once it hasmerged=true.Description
This PR fixes tree-model pure-data pipe synchronization when the receiver does not already have the source tree database.
For pipe-generated tree inserts and TsFile loads, the receiver may carry an explicit tree database hint such as
root.test.sg_0. Partition analysis uses this explicit database name directly, so the normal tree device-path based database auto-creation path is bypassed. As a result, receiver-side writes can repeatedly fail withCreate DataPartition failed because the database ... is not exists.Semantics
Receiver-side tree database creation follows these rules:
The PR:
Verification
mvn -DskipTests spotless:apply -pl iotdb-core/datanodegit diff --checkmvn -Ddevelocity.off=true compile -pl iotdb-core/datanodewas also attempted, but the current workspace fails in unrelated existing datanode/generated sources, e.g. missingAccumulator,IFill,LinearFill,PipeProcessorSubtask#getDisplayTaskID(), and related symbols.