JNSimba opened a new pull request, #719: URL: https://github.com/apache/doris-flink-connector/pull/719
# Proposed changes Issue Number: N/A ## Problem Summary Closing a Flight SQL reader currently releases the local ADBC resources but leaves its authenticated session on the FE. Repeated snapshot or changelog splits accumulate idle sessions even after the reading process exits. Send CloseSession using the existing authenticated client before closing the ADBC connection. Cleanup is idempotent and the RPC has a five-second deadline; remote cleanup failures are logged while local resource cleanup continues. A small adapter validates and accesses the pinned ADBC driver's internal client and authentication options because its public connection interface does not expose CloseSession. Use ADBC 0.14.0 and Arrow 17.0.0 to retain Java 8 compatibility and use the official CloseSession API. Align Arrow and protobuf modules through BOMs, and merge service registrations in both shaded connector artifacts so gRPC providers remain available. ## Validation - Base module: 485 tests, zero failures/errors, one skipped, including authenticated session cleanup, duplicate close, server rejection, an unresponsive server deadline, and initialization failure cleanup. - Flink 1.20 and Flink 2.3 connector reactor packaging passed. - On a real Doris cluster with FE/BE changelog enabled and a table with changelog enabled, ran the final shaded artifacts on JDK 1.8.0_331. Each snapshot and DETAIL changelog scenario read ten splits with three validated rows per split. The original version left ten additional idle sessions in each scenario; the fixed version left zero. Session IDs were compared to ensure existing sessions did not disappear and mask new leaks. - The Flink 1.x shaded artifact contains no ordinary class files above Java 8 bytecode level (excluding module descriptors and multi-release entries). ## Checklist(Required) 1. Does it affect the original behavior: Yes; Flight SQL readers now explicitly close their remote sessions. 2. Has unit tests been added: Yes. 3. Has document been added or modified: No Need. 4. Does it need to update dependencies: Yes. 5. Are there any changes that cannot be rolled back: No. ## Further comments The adapter depends on the pinned ADBC driver's internal field layout and must be revalidated for future dependency upgrades. Connection reuse is outside this change. Real-cluster validation exercised the connector reader directly; a complete Flink job, TLS, and the full release compatibility matrix were not exercised. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
