Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/280#issuecomment-65757536
I think that around ```checkAndInitializeSystemDirectories()``` method
would be the best place for the startup diagnosis of TajoMaster. Also,
serviceInit() would be the best place for TajoWorker. The constructor of
TajoClient would best.
Your patch already includes two rules: Hadoop runtime version check and
TajoConf verification. Both are necessary in TajoMaster and TajoWorker
components. Since Hadoop dependency will be removed from TajoClient (see
https://issues.apache.org/jira/browse/TAJO-1160), only TajoConf verification
would be necessary in TajoClient.
Cheers,
Hyunsik
---
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.
---
