Emor-nj opened a new issue, #5987:
URL: https://github.com/apache/kyuubi/issues/5987

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the 
[issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Describe the bug
   
   When using Kyuubi in my company, there is a scenario where we create a 
symbolic link from ${KYUUBI_HOME}/bin/beeline to /usr/bin/kyuubi-beeline. This 
allows distinguishing its usage from Hive's beeline, and users can globally use 
kyuubi-beeline without specifying a directory. However, when executing 
kyuubi-beeline, an error occurs, stating that it cannot find 
load-kyuubi-env.sh. The specific error message is as follows:**_" 
/bin/kyuubi-beeline: line 25: //bin/load-kyuubi-env.sh: No such file or 
directory."_** 
   
   Personally, I believe the logic of exporting KYUUBI_HOME in 
${KYUUBI_HOME}/bin/beeline should be modified. If the environment has already 
declared KYUUBI_HOME, it should use the pre-declared KYUUBI_HOME instead of 
forcefully specifying the parent directory of the current one.
   
   ### Affects Version(s)
   
   master/1.8.0
   
   ### Kyuubi Server Log Output
   
   _No response_
   
   ### Kyuubi Engine Log Output
   
   _No response_
   
   ### Kyuubi Server Configurations
   
   _No response_
   
   ### Kyuubi Engine Configurations
   
   _No response_
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes. I would be willing to submit a PR with guidance from the Kyuubi 
community to fix.
   - [ ] No. I cannot submit a PR at this time.


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