Skip to content

[dev/1.3] Fix JDBC batch failure reporting - #19261

Merged
Caideyipi merged 1 commit into
dev/1.3from
backport/19245-dev-1.3
Nov 16, 2026
Merged

Caideyipi merged 1 commit into
dev/1.3from
backport/19245-dev-1.3

Conversation

@Caideyipi

Copy link
Copy Markdown
Collaborator

Backport the applicable parts of #19245 (594a237) to dev/1.3.

Batch statements whose execution returns an error status can currently be reported as successful because only thrown exceptions clear the success flag. Check every execution result so JDBC receives the per-statement failures and raises BatchUpdateException, while keeping success and redirection statuses accepted.

Also retain the two BLOB fixture corrections from the original commit in IoTDBReplaceFunctionIT and IoTDBSubStringFunctionIT. The table-model database synchronization change and five tests absent from dev/1.3 are omitted during conflict resolution.

Validation:

  • Passed: mvn spotless:apply -P with-integration-tests -pl iotdb-core/datanode,integration-test.
  • Passed: git diff --cached --check before committing.
  • Not run: compilation and the focused integration tests. Clean source verification was blocked before compilation by Maven extension dependency resolution; connectivity probes to public dependency repositories also timed out.

* Fix JDBC batch failure status handling

* Fix invalid integration test fixtures exposed by batch error reporting

* Fix legacy table IT setup data

(cherry picked from commit 594a237)
@sonarqubecloud

Copy link
Copy Markdown

@Caideyipi
Caideyipi merged commit 2bbcb3d into dev/1.3 Nov 16, 2026
17 of 18 checks passed
@Caideyipi
Caideyipi deleted the backport/19245-dev-1.3 branch November 16, 2026 03:39
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