abhishekacharya200 opened a new pull request, #75128:
URL: https://github.com/apache/airflow/pull/75128
QdrantClient names this option `prefer_grpc`, so a Qdrant connection defined
in JSON or an environment variable, for example with `{"prefer_grpc": true}` in
the extra, naturally uses that key. The hook only read `prefer_gprc`, the
misspelled key the connection form saves, so those connections silently stayed
on REST.
The hook now reads `prefer_grpc` and falls back to `prefer_gprc`, so
connections saved through the form keep working with no migration. When both
keys are set, `prefer_grpc` takes precedence. I left the form field and
`provider.yaml` on the old key on purpose: the form hides the raw extra, so
renaming the key there would leave a stale value behind that users could not
see or remove. The connection docs now say which key to use.
The new test defines the connection through an `AIRFLOW_CONN_QDRANT_DEFAULT`
environment variable (with the `create_connection_without_db` fixture) and
checks the value that reaches `QdrantClient`. Both cases fail on main and pass
with this change.
Checks I ran locally:
* `uv run --project providers/qdrant pytest
providers/qdrant/tests/unit/qdrant/hooks/test_qdrant.py`: 10 passed
* `prek run --stage pre-commit` on the changed files: all passed. The Breeze
based hooks (such as the provider.yaml validation) were skipped with
`SKIP_BREEZE_PREK_HOOKS`, because I could not run the Breeze image locally;
`provider.yaml` is unchanged.
* mypy 2.3.1 with the repository config on the changed files: no issues
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Opus 5.5) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
