kingswanwho opened a new issue #2231:
URL: https://github.com/apache/drill/issues/2231


   **Describe the bug**
   My JAVA_PATH set to "/Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home",
   when run `./drillbit.sh start`, drill cannot startup and report error:
   ` /Users/Chester/Gwssi/ApacheDrill/apache-drill-1.19.0-SNAPSHOT/bin/runbit: 
line 109: /Library/Internet: No such file or directory`  
   `/Users/Chester/Gwssi/ApacheDrill/apache-drill-1.19.0-SNAPSHOT/bin/runbit: 
line 109: exec: /Library/Internet: cannot execute: No such file or directory`
   
   **To Reproduce**
   Steps to reproduce the behavior:  
   1. set JAVA_PATH to a jdk path which contains whitespace:  
   `export JAVA_PATH=/Library/Internet 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home`
   2. startup drill:  
   `./bin/drillbit.sh start`
   3. See error in log file:  
   `log/drillbit.out`
   
   **Expected behavior**
   Drill cannot startup normally.
   
   **Screenshots**
   
![image](https://user-images.githubusercontent.com/15710469/118493228-77805600-b753-11eb-89f0-0bc677cf0f74.png)
   
![image](https://user-images.githubusercontent.com/15710469/118493303-8a932600-b753-11eb-8cf6-418bcd3e23e0.png)
   
   **Desktop (please complete the following information):**
    - MacOS Big Sur 11.2.3 
   
   **Additional context**
   print the command of line 109 in runbit:
   `echo exec $BITCMD`  
   
   See the print result in `log/drillbit.out`:  
   
![image](https://user-images.githubusercontent.com/15710469/118494219-8582a680-b754-11eb-8957-3f52a6a2de61.png)
   We can see that the whitespace in java path doesn't come up with a backslash 
escape, so that `exec` cannot find the correct java path.
   After I set the java path without white space, like:  
   `/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home`  
   Drill startup process back to normal.
   
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to