[
https://issues.apache.org/jira/browse/STORM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987832#comment-14987832
]
ASF GitHub Bot commented on STORM-876:
--------------------------------------
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/845#discussion_r43788291
--- Diff: bin/storm.py ---
@@ -263,6 +263,34 @@ def upload_credentials(*args):
jvmtype="-client",
extrajars=[USER_CONF_DIR, STORM_BIN_DIR])
+def blobstore(*args):
+ """Syntax: [storm blobstore [cmd]]
+
+ list [KEY...] - lists blobs currently in the blob store
+ cat [-f FILE] KEY - read a blob and then either write it to a file, or
STDOUT (requires read access).
+ create [-f FILE] [-a ACL ...] [--repl-fctr NUMBER] KEY - create a new
blob. Contents comes from a FILE
+ or STDIN. ACL is in the form [uo]:[username]:[r-][w-][a-] can be
comma
+ separated list.
--- End diff --
Documentation suggestions:
It might be good to add a brief example here of an ACL, as we have the same
for the replication factor. Technically, the Access Control List is a list of
entries, each of the form `<u:USERNAME:[r-][w-][a-] | o::[r-][w-][a-]>[,...]`
`For example, to allow everyone read access and to allow alice read, write,
and admin access, the ACL would have two entries: "o::r,u:alice:rwa"`
Since there are multiple commands that take ACL option arguments, we might
want to just add some "ACL Example" to the end of the help text.
> Dist Cache: Basic Functionality
> -------------------------------
>
> Key: STORM-876
> URL: https://issues.apache.org/jira/browse/STORM-876
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Attachments: DISTCACHE.md, DistributedCacheDesignDocument.pdf
>
>
> Basic functionality for the Dist Cache feature.
> As part of this a new API should be added to support uploading and
> downloading dist cache items. storm-core.ser, storm-conf.ser and storm.jar
> should be written into the blob store instead of residing locally. We need a
> default implementation of the blob store that does essentially what nimbus
> currently does and does not need anything extra. But having an HDFS backend
> too would be great for scalability and HA.
> The supervisor should provide a way to download and manage these blobs and
> provide a working directory for the worker process with symlinks to the
> blobs. It should also allow the blobs to be updated and switch the symlink
> atomically to point to the new blob once it is downloaded.
> All of this is already done by code internal to Yahoo! we are in the process
> of getting it ready to push back to open source shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
