[
https://issues.apache.org/jira/browse/TWILL-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438619#comment-15438619
]
ASF GitHub Bot commented on TWILL-185:
--------------------------------------
GitHub user anwar6953 opened a pull request:
https://github.com/apache/twill/pull/7
TWILL-185 Allow user to avoid scheduling the LocationSecureStoreUpdater.
This will allow the use case of user scheduling their own secure store
updates.
As a workaround, for example:
https://github.com/caskdata/cdap/pull/6380/commits/e77b9ac1fa6c9176a49cb27d6118e2d3065b93cd#diff-832334ca819881b7884d50946c76ce00L332
It will also alleviate some of the issues described in
https://issues.apache.org/jira/browse/TWILL-109.
https://issues.apache.org/jira/browse/TWILL-185
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anwar6953/twill
feature/allow-disabling-secure-store-update
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/twill/pull/7.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 #7
----
commit 12debc95d517561b5a88057c842d4697d87f8fc9
Author: Ali Anwar <anw...@berkeley.edu>
Date: 2016-08-26T07:37:14Z
TWILL-185 Allow user to avoid scheduling the LocationSecureStoreUpdater.
----
> Allow user to disable the SecureStoreUpdater in Twill
> -----------------------------------------------------
>
> Key: TWILL-185
> URL: https://issues.apache.org/jira/browse/TWILL-185
> Project: Apache Twill
> Issue Type: Improvement
> Components: api
> Affects Versions: 0.7.0-incubating
> Reporter: Ali Anwar
> Fix For: 0.8.0
>
>
> User can have their own SecureStoreUpdater scheduled.
> Having two of these schedules can cause issues (see TWILL-109).
> It also can cause conflicts with the updating done by the user's
> SecureStoreUpdater.
> Allowing the user to disable the SecureStoreUpdater in Twill is a simple way
> to resolve both of these issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
