You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by dongjinleekr <gi...@git.apache.org> on 2016/10/18 12:14:10 UTC
[GitHub] tajo pull request #1051: TAJO-2184: Can not run Tajo with non-default $TAJO_...
GitHub user dongjinleekr opened a pull request:
https://github.com/apache/tajo/pull/1051
TAJO-2184: Can not run Tajo with non-default $TAJO_CONF_DIR
start-tajo.sh was updated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dongjinleekr/tajo feature/TAJO-2184
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/1051.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1051
----
commit b2b21c0b3e226258d858e9c269936cebbfa59876
Author: Lee Dongjin <do...@apache.org>
Date: 2016-10-18T12:12:41Z
Update start-tajo.sh: add '--config' parameter when running tajo-daemon.sh
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo issue #1051: TAJO-2184: Can not run Tajo with non-default $TAJO_CONF_DI...
Posted by eminency <gi...@git.apache.org>.
Github user eminency commented on the issue:
https://github.com/apache/tajo/pull/1051
Hi, @dongjinleekr. Thanks for the contribution.
Though I reviewed briefly, it seems **--config** parameter is passed only to tajo-daemon.sh, not to tajo-daemons.sh.
Could you check it out?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo issue #1051: TAJO-2184: Can not run Tajo with non-default $TAJO_CONF_DI...
Posted by hyunsik <gi...@git.apache.org>.
Github user hyunsik commented on the issue:
https://github.com/apache/tajo/pull/1051
FYI, as Dongjin said, tajo-daemon.sh is an actual script to be executed at each node. tajo-daemons is a script to call iteratively a given command in all remote nodes.
---
[GitHub] tajo issue #1051: TAJO-2184: Can not run Tajo with non-default $TAJO_CONF_DI...
Posted by dongjinleekr <gi...@git.apache.org>.
Github user dongjinleekr commented on the issue:
https://github.com/apache/tajo/pull/1051
Sure. I already checked it out. As you can see from tajo-daemon.sh and tajo-daemons.sh, only the first one takes --config parameter; the second one works as a ssh-proxy to the worker hosts. By this reason, it is sufficient to pass the parameter only to tajo-daemon.sh. (In detail, tajo-daemons.sh passes the execution command of tajo-daemon.sh to the workers via its parameters, including --config.)
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo pull request #1051: TAJO-2184: Can not run Tajo with non-default $TAJO_...
Posted by hyunsik <gi...@git.apache.org>.
Github user hyunsik closed the pull request at:
https://github.com/apache/tajo/pull/1051
---