[
https://issues.apache.org/jira/browse/TWILL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467992#comment-15467992
]
Terence Yim commented on TWILL-189:
-----------------------------------
Shall we remove the {{<T> T getStore()}} method then? Since now's it's the
{{SecureStore}} responsibility to write to a given location? By the way,
instead of giving a {{URI}}, I think it's better to have the method as:
{{void persist(OutputProvider<OutputStream> osProvider)}}
with {{OutputProvider}} has a single method {{OutputStream open()}}.
With that, the user doesn't need to handle the URI by himself. With this API, I
believe we also need to fix the {{LocationFactory}} implementations (HDFS and
FileContext) to have the {{create}} method always use the current UGI to open
the stream, instead of the cached one.
> 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.8.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.4#6332)
