goutamadwant opened a new pull request, #12843: URL: https://github.com/apache/seatunnel/pull/12843
### Purpose of this pull request This contribution fixes SeaTunnel's Qdrant authentication path. The source and sink accept `api_key`, but the shared client builder does not apply it, so authenticated jobs fail with `UNAUTHENTICATED`. The change passes a nonempty configured key to the shared gRPC client builder. It adds an authenticated source-to-sink E2E case and clarifies TLS guidance in the English and Chinese connector docs. Fixes #12842 ### Does this PR introduce _any_ user-facing change? Yes. Before this change, setting the correct `api_key` did not authenticate Qdrant connections. After this change, both source and sink use the configured key. No option names, defaults, dependencies, or public APIs change. Jobs without a key retain anonymous behavior. A nonempty key is now sent instead of being silently ignored; remove it if anonymous access is intended. ### How was this patch tested? - Before the production fix, the authenticated E2E job failed against Qdrant v1.15.0 with `UNAUTHENTICATED: Must provide an API key or an Authorization bearer token`. - After the fix, `QdrantIT` passed both authenticated and anonymous source-to-sink jobs through the local Zeta engine on Java 11: 2 tests, 0 failures. - Scoped connector build, formatting, and diff checks passed. - Full repository CI and a TLS-enabled Qdrant endpoint were not tested locally. ### Check list * [x] No new JAR binary package was added. * [x] English and Chinese connector documentation was updated. * [x] No incompatible change or migration note is needed. * [x] Existing connector metadata needs no change; the Qdrant E2E test was extended. -- 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]
