You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by blrunner <gi...@git.apache.org> on 2015/12/02 09:46:31 UTC

[GitHub] tajo pull request: Change log4j log level for aws

GitHub user blrunner opened a pull request:

    https://github.com/apache/tajo/pull/893

    Change log4j log level for aws

    I found that the patch ran as expected on emr cluster.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/blrunner/tajo TAJO-2002

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/893.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 #893
    
----
commit 6d3ff13380909ee88c6715da5fa83cbe958abd07
Author: JaeHwa Jung <bl...@apache.org>
Date:   2015-12-02T08:45:03Z

    Change log4j log level for aws

----


---
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: Change log4j log level for aws

Posted by dkhwangbo <gi...@git.apache.org>.

Github user dkhwangbo commented on the pull request:

    https://github.com/apache/tajo/pull/893#issuecomment-161632279
  
    I have a question.
    This patch has no mention about s3, s3n. just s3a is written. Can I get a explanation about it?


---
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: TAJO-2002: Change log4j log level for aws

Posted by blrunner <gi...@git.apache.org>.

Github user blrunner closed the pull request at:

    https://github.com/apache/tajo/pull/893


---
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: Change log4j log level for aws

Posted by blrunner <gi...@git.apache.org>.

Github user blrunner commented on the pull request:

    https://github.com/apache/tajo/pull/893#issuecomment-161849640
  
    @dkhwangbo 
    
    Honestly, I borrowed line 1,2,3 from hadoop default configuration.
    For the reference, when I testing the patch with ```s://`` prefix on EMR, I couldn't see any log messages for S3Filesystem.


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