shashihoushengqia opened a new issue, #62338: URL: https://github.com/apache/airflow/issues/62338
### Apache Airflow version 3.1.7 ### If "Other Airflow 3 version" selected, which one? _No response_ ### What happened? When creating a Hive Server 2 Thrift connection using Airflow, no matter how the password is modified, Airflow will always change it to a "x" character. ### What you think should happen instead? _No response_ ### How to reproduce 1. Create a Hive Server 2 Thrift connection: <img width="1210" height="1111" alt="Image" src="https://github.com/user-attachments/assets/15acf152-a4c1-4b5e-a25d-8b434dda3cd1" /> 2. Create a DAG: <img width="2358" height="906" alt="Image" src="https://github.com/user-attachments/assets/821a66d2-d675-41cc-8445-85c477d60fe6" /> 3. Manually trigger the DAG and perform network packet capture on the Hive end: <img width="1006" height="417" alt="Image" src="https://github.com/user-attachments/assets/47a7d14c-722c-4ab3-be43-c5c60f9d18bd" /> Here it is shown that Airflow sent a data packet to Hive with the Username "airflow_test_user" and the Password "x". At this point, the password I set as "123456789" has disappeared and I have also tried setting other passwords, but without exception, they were all changed to "x". ### Operating System Debian GNU/Linux 12 (bookworm) ### Versions of Apache Airflow Providers apache-airflow-providers-apache-hive==9.2.5 ### Deployment Official Apache Airflow Helm Chart ### Deployment details k3s: v1.32.12+k3s1 Airflow: v3.1.7 helm-chart: v1.19.0 ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
