ada-nilova opened a new issue, #40805:
URL: https://github.com/apache/airflow/issues/40805

   ### Apache Airflow Provider(s)
   
   apache-hive
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-apache-hive==8.1.1
   
   ### Apache Airflow version
   
   2.8.4
   
   ### Operating System
   
   Debian GNU/Linux 12
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   In [#38651](https://github.com/apache/airflow/pull/38651) to 
airflow/providers/apache/hive/hooks/hive.py was added hardcoded URL part with 
"zooKeeperNamespace=hiveserver2".
   Unfortunately, "hiveserver2" is not the once namespace name what can be. In 
some Hadoop installations zooKeeperNamespace can have any custom name. 
   
   In the same change was added ssl using always and only when using HA. But in 
some Hadoop installations we can set using ssl, but not using HA. And now we 
cannot use one option separately from another.
   
   ### What you think should happen instead
   
   If we check HA checkbox, it should be better to have a field for custom 
zooKeeperNamespace name in a connection form, not hardcoded.
   
   And it should be better to have a special checkbox for ssl setting, 
separately from a HA checkbox
   
   ### How to reproduce
   
   If we have another zooKeeperNamespace (not hiveserver2) we cannot use 
HiveOperator with it.
   
   If we have Hive with SSL, but without Zookeeper we cannot use HiveOperator 
with it.
   
   
   ### 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]

Reply via email to