Skip to content

branch-4.0: [fix](regression) Avoid prepared Arrow JDBC path in remote IP auth test #64024#64047

Open
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64024-branch-4.0
Open

branch-4.0: [fix](regression) Avoid prepared Arrow JDBC path in remote IP auth test #64024#64047
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64024-branch-4.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 3, 2026

Cherry-picked from #64024

…st (#64024)

### What problem does this PR solve?

Related PR: [63506](#63506)

Problem Summary: `test_auth_remote_ip` only needs to verify that Arrow
Flight SQL remote IP authentication allows a matched user to run `SELECT
1`. The shared `sql_impl` helper uses `PreparedStatement`, and Arrow
Flight SQL JDBC 17 can report a close-time 8-byte client allocator leak
after the prepared path has already consumed the result. This changes
the case to use `JdbcUtils.executeQueryToList`, which uses
`createStatement().executeQuery(...)`, so the test avoids the prepared
statement cleanup path without ignoring `conn.close()` exceptions.
@github-actions github-actions Bot requested a review from morningman as a code owner June 3, 2026 03:43
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

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