Skip to content

Reclaim the statement variable to avoid executing stale statements in the subsequent new test case - #18001

Merged
HTHou merged 3 commits into
apache:masterfrom
zerolbsony:reclaim-statement-var
Jun 23, 2026
Merged

HTHou merged 3 commits into
apache:masterfrom
zerolbsony:reclaim-statement-var

Conversation

@zerolbsony

Copy link
Copy Markdown
Contributor

No description provided.

@HTHou HTHou left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One cleanup concern in integration-test/src/test/java/org/apache/iotdb/db/it/utils/TestUtils.java around line 1212:

Statement.close() can itself throw SQLException. Since it now runs before localConnection.close() in the same try, a close failure here would skip closing the local connection and can leak it on the retry path. Could you split the statement and connection closes into separate try/catch blocks, or otherwise ensure localConnection.close() is still attempted even when closing the statement fails?

@HTHou
HTHou merged commit b727c66 into apache:master Jun 23, 2026
40 checks passed
MileaRobertStefan pushed a commit to MileaRobertStefan/iotdb that referenced this pull request Jun 26, 2026
… the subsequent new test case (apache#18001)

* Reclaim the statement variable to avoid executing stale statements in the subsequent new test case.

* Don't affect the connection closing any more

* Fix
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.

2 participants