[jira] [Resolved] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terence Yim resolved TWILL-229. --- Resolution: Fixed > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950004#comment-15950004 ] ASF GitHub Bot commented on TWILL-229: -- Github user asfgit closed the pull request at: https://github.com/apache/twill/pull/49 > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill pull request #49: (TWILL-229) Default to use logback_template.xml to c...
Github user asfgit closed the pull request at: https://github.com/apache/twill/pull/49 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-189) SecureStoreUpdater should support updating secure store as other users
[ https://issues.apache.org/jira/browse/TWILL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1595#comment-1595 ] ASF GitHub Bot commented on TWILL-189: -- Github user chtyim commented on the issue: https://github.com/apache/twill/pull/48 I tried to create a unit test using MiniKdc, but seems like I hit this bug https://issues.apache.org/jira/browse/HDFS-9213 > SecureStoreUpdater should support updating secure store as other users > -- > > Key: TWILL-189 > URL: https://issues.apache.org/jira/browse/TWILL-189 > Project: Apache Twill > Issue Type: New Feature > Components: api >Affects Versions: 0.7.0-incubating >Reporter: Ali Anwar > Fix For: 0.11.0 > > > SecureStoreUpdater always creates secure stores for the current user and > writes these as the current user. > It should allow writing the secure store as a different user. > For an example use case, see: https://github.com/caskdata/cdap/pull/6380 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill issue #48: (TWILL-189) Allows secure store update with different UGI
Github user chtyim commented on the issue: https://github.com/apache/twill/pull/48 I tried to create a unit test using MiniKdc, but seems like I hit this bug https://issues.apache.org/jira/browse/HDFS-9213 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949967#comment-15949967 ] ASF GitHub Bot commented on TWILL-229: -- Github user yaojiefeng commented on the issue: https://github.com/apache/twill/pull/49 I see. LGTM > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill issue #49: (TWILL-229) Default to use logback_template.xml to configur...
Github user yaojiefeng commented on the issue: https://github.com/apache/twill/pull/49 I see. LGTM --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949960#comment-15949960 ] ASF GitHub Bot commented on TWILL-229: -- Github user chtyim commented on the issue: https://github.com/apache/twill/pull/49 For AM, currently it is not settable. For Runnable containers, user can add as resources / localize a `logback.xml` file and specify it in the classpath. > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill issue #49: (TWILL-229) Default to use logback_template.xml to configur...
Github user chtyim commented on the issue: https://github.com/apache/twill/pull/49 For AM, currently it is not settable. For Runnable containers, user can add as resources / localize a `logback.xml` file and specify it in the classpath. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949900#comment-15949900 ] ASF GitHub Bot commented on TWILL-229: -- Github user yaojiefeng commented on the issue: https://github.com/apache/twill/pull/49 Changes LGTM, may I ask where do we set the logback if it is overriden by user? > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill issue #49: (TWILL-229) Default to use logback_template.xml to configur...
Github user yaojiefeng commented on the issue: https://github.com/apache/twill/pull/49 Changes LGTM, may I ask where do we set the logback if it is overriden by user? --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949867#comment-15949867 ] ASF GitHub Bot commented on TWILL-229: -- GitHub user chtyim opened a pull request: https://github.com/apache/twill/pull/49 (TWILL-229) Default to use logback_template.xml to configure logger, … …unless overridden by user You can merge this pull request into a Git repository by running: $ git pull https://github.com/chtyim/twill feature/TWILL-229 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/twill/pull/49.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 #49 commit 8aaa15af3132b35fded7424011c1f2a37ef14648 Author: Terence Yim Date: 2017-03-30T21:23:36Z (TWILL-229) Default to use logback_template.xml to configure logger, unless overridden by user > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill pull request #49: (TWILL-229) Default to use logback_template.xml to c...
GitHub user chtyim opened a pull request: https://github.com/apache/twill/pull/49 (TWILL-229) Default to use logback_template.xml to configure logger, ⦠â¦unless overridden by user You can merge this pull request into a Git repository by running: $ git pull https://github.com/chtyim/twill feature/TWILL-229 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/twill/pull/49.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 #49 commit 8aaa15af3132b35fded7424011c1f2a37ef14648 Author: Terence Yim Date: 2017-03-30T21:23:36Z (TWILL-229) Default to use logback_template.xml to configure logger, unless overridden by user --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terence Yim updated TWILL-229: -- Fix Version/s: 0.11.0 > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TWILL-229) Use the logback_template.xml as the default logback configuration
Terence Yim created TWILL-229: - Summary: Use the logback_template.xml as the default logback configuration Key: TWILL-229 URL: https://issues.apache.org/jira/browse/TWILL-229 Project: Apache Twill Issue Type: Bug Reporter: Terence Yim Assignee: Terence Yim It is a regression created by TWILL-122. Without using the logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TWILL-229) Use the logback_template.xml as the default logback configuration
[ https://issues.apache.org/jira/browse/TWILL-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Terence Yim updated TWILL-229: -- Affects Version/s: 0.11.0 > Use the logback_template.xml as the default logback configuration > - > > Key: TWILL-229 > URL: https://issues.apache.org/jira/browse/TWILL-229 > Project: Apache Twill > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: Terence Yim >Assignee: Terence Yim > Fix For: 0.11.0 > > > It is a regression created by TWILL-122. Without using the > logback_template.xml as the default, the AM logs extensively. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TWILL-189) SecureStoreUpdater should support updating secure store as other users
[ https://issues.apache.org/jira/browse/TWILL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948658#comment-15948658 ] ASF GitHub Bot commented on TWILL-189: -- GitHub user chtyim opened a pull request: https://github.com/apache/twill/pull/48 (TWILL-189) Allows secure store update with different UGI - Deprecated the old TwillRunner.scheduleSecureStoreUpdate - Added new TwillRunner.setSecureStoreRenewer method - Takes SecureStoreRenewer that writes SecureStore via SecureStoreWriter - The renewer implementation can use appropriate UGI.doAs to make call to SecureStoreWriter You can merge this pull request into a Git repository by running: $ git pull https://github.com/chtyim/twill feature/TWILL-189 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/twill/pull/48.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 #48 commit 292008e903866b828e32d5a93aa2a7b6775e46c7 Author: Terence Yim Date: 2017-03-28T21:31:06Z (TWILL-189) Allows secure store update with different UGI - Deprecated the old TwillRunner.scheduleSecureStoreUpdate - Added new TwillRunner.setSecureStoreRenewer method - Takes SecureStoreRenewer that writes SecureStore via SecureStoreWriter - The renewer implementation can use appropriate UGI.doAs to make call to SecureStoreWriter > SecureStoreUpdater should support updating secure store as other users > -- > > Key: TWILL-189 > URL: https://issues.apache.org/jira/browse/TWILL-189 > Project: Apache Twill > Issue Type: New Feature > Components: api >Affects Versions: 0.7.0-incubating >Reporter: Ali Anwar > Fix For: 0.11.0 > > > SecureStoreUpdater always creates secure stores for the current user and > writes these as the current user. > It should allow writing the secure store as a different user. > For an example use case, see: https://github.com/caskdata/cdap/pull/6380 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] twill pull request #48: (TWILL-189) Allows secure store update with differen...
GitHub user chtyim opened a pull request: https://github.com/apache/twill/pull/48 (TWILL-189) Allows secure store update with different UGI - Deprecated the old TwillRunner.scheduleSecureStoreUpdate - Added new TwillRunner.setSecureStoreRenewer method - Takes SecureStoreRenewer that writes SecureStore via SecureStoreWriter - The renewer implementation can use appropriate UGI.doAs to make call to SecureStoreWriter You can merge this pull request into a Git repository by running: $ git pull https://github.com/chtyim/twill feature/TWILL-189 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/twill/pull/48.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 #48 commit 292008e903866b828e32d5a93aa2a7b6775e46c7 Author: Terence Yim Date: 2017-03-28T21:31:06Z (TWILL-189) Allows secure store update with different UGI - Deprecated the old TwillRunner.scheduleSecureStoreUpdate - Added new TwillRunner.setSecureStoreRenewer method - Takes SecureStoreRenewer that writes SecureStore via SecureStoreWriter - The renewer implementation can use appropriate UGI.doAs to make call to SecureStoreWriter --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TWILL-223) FileContextLocationFactory should use FileContext instance based on the caller UGI
[
https://issues.apache.org/jira/browse/TWILL-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948631#comment-15948631
]
ASF GitHub Bot commented on TWILL-223:
--
Github user asfgit closed the pull request at:
https://github.com/apache/twill/pull/47
> FileContextLocationFactory should use FileContext instance based on the
> caller UGI
> --
>
> Key: TWILL-223
> URL: https://issues.apache.org/jira/browse/TWILL-223
> Project: Apache Twill
> Issue Type: Bug
>Reporter: Terence Yim
>Assignee: Terence Yim
> Fix For: 0.11.0
>
>
> The {{FileContextLocationFactory}} internally has a cached {{FileContext}}
> object that was created when the factory was created. However, when the
> {{getFileContext}} is called (directly or via one of those {{create}}
> methods), the UGI might be different then the cached one. If the cached one
> is returning, FS operations will be performed with the user who creates the
> factory, not the one who calls the {{create}} method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (TWILL-223) FileContextLocationFactory should use FileContext instance based on the caller UGI
[
https://issues.apache.org/jira/browse/TWILL-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Terence Yim resolved TWILL-223.
---
Resolution: Fixed
> FileContextLocationFactory should use FileContext instance based on the
> caller UGI
> --
>
> Key: TWILL-223
> URL: https://issues.apache.org/jira/browse/TWILL-223
> Project: Apache Twill
> Issue Type: Bug
>Reporter: Terence Yim
>Assignee: Terence Yim
> Fix For: 0.11.0
>
>
> The {{FileContextLocationFactory}} internally has a cached {{FileContext}}
> object that was created when the factory was created. However, when the
> {{getFileContext}} is called (directly or via one of those {{create}}
> methods), the UGI might be different then the cached one. If the cached one
> is returning, FS operations will be performed with the user who creates the
> factory, not the one who calls the {{create}} method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] twill pull request #47: (TWILL-223) Make FileContextLocationFactory UGI awar...
Github user asfgit closed the pull request at: https://github.com/apache/twill/pull/47 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
