pan3793 opened a new pull request, #6239:
URL: https://github.com/apache/kyuubi/pull/6239

   # :mag: Description
   
   Discussion in mailing thread: 
https://lists.apache.org/thread/tnmz71o3rypy7qvs3899p3jkkq4xqb4r
   
   I propose to rename the `bin/beeline` to `bin/kyuubi-beeline`, while for 
compatibility, we may still want to keep the alias `bin/beeline` for a while.
   
   In a real Hadoop cluster, it’s likely to add `$HIVE_HOME/bin`, 
`$SPARK_HOME/bin`, `$KYUUBI_HOME/bin` to the `$PATH`, at the current state, 
when performing `beeline`, which one is called depends on the declaration order.
   
   It does not matter for Spark’s `bin/beeline` because it’s a vanilla Hive 
BeeLine, but in Kyuubi, we have made some improvements based on vanilla Hive 
BeeLine, so the behavior is not exactly same as Hive’s BeeLine.
   
   An identical name would solve this problem. And I saw some vendors[1] who 
shippes Kyuubi already have done the same thing.
   
   [1] https://help.aliyun.com/zh/emr/emr-on-ecs/user-guide/connect-to-kyuubi
   
   ## Types of changes :bookmark:
   <!--- What types of changes does your code introduce? Put an `x` in all the 
boxes that apply: -->
   - [ ] Bugfix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   
   ## Test Plan 🧪
   
   Manual test. (TODO)
   
   ---
   
   # Checklist 📝
   <!--- Go over all the following points, and put an `x` in all the boxes that 
apply. -->
   <!--- If you're unsure about any of these, don't hesitate to ask. We're here 
to help! -->
   
   - [x] This patch was not authored or co-authored using [Generative 
Tooling](https://www.apache.org/legal/generative-tooling.html)
   
   **Be nice. Be informative.**
   


-- 
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]

Reply via email to