Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/1002#issuecomment-212601155
There is some potential problem. The original implement forces users to
specific JAVA_HOME. As a result, users must set JAVA_HOME.
This change allows users to not specific JAVA_HOME. If users do not set
JAVA_HOME, Tajo can run on different JVMs across multiple nodes. It may cause
critical problem because we are using unsafe codes in some parts.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
