Skip to content

Fix pipe tsfile receiver database handling#17815

Open
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix/pipe-tsfile-database-level
Open

Fix pipe tsfile receiver database handling#17815
Caideyipi wants to merge 1 commit into
apache:masterfrom
Caideyipi:fix/pipe-tsfile-database-level

Conversation

@Caideyipi
Copy link
Copy Markdown
Collaborator

Description

This patch fixes pipe tsfile receiver behavior when the sender provides a tree database name such as
oot.test.sg_0:

  • derive the tree database level from the provided database name for sync tsfile load, so
    oot.test.sg_0 uses database level 2 instead of the receiver default
  • apply the same derived database level to async active-load attributes so async and sync pipe tsfile load behave consistently
  • classify IoTDBRuntimeException(DATABASE_NOT_EXIST) as PIPE_RECEIVER_PARALLEL_OR_USER_CONFLICT_EXCEPTION, matching the TSStatus visitor path instead of returning 305
  • reduce repeated receiver statement exception WARN stack logs via the existing PipePeriodicalLogReducer style

Tests

  • mvn spotless:apply -pl iotdb-core/datanode
  • git diff --check
  • mvn '-Ddevelocity.off=true' '-Dcheckstyle.skip=true' '-DargLine=-Xmx512m' test -pl iotdb-core/datanode '-Dtest=IoTDBDataNodeReceiverTest,PipeStatementTsStatusVisitorTest,LoadTsFileStatementTest'
    • blocked before test execution by existing generated-source compilation errors in arget/generated-sources/freemarker/.../*ModeAccumulator.java (ComparatorChain missing and IoTDBConfig.getModeMapSizeThreshold() missing)

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.

1 participant