[ 
https://issues.apache.org/jira/browse/STORM-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932270#comment-15932270
 ] 

Jungtaek Lim commented on STORM-2038:
-------------------------------------

[~JanecekPetr]
I've just merged the patch for all 1.x / 2.x version lines so you can pull the 
change, and build, and give it a try.
Setting `storm.disable.symlinks: true` to storm.yaml for every nodes should 
work for Windows with account which is not able to make symlink.

> Provide an alternative to using symlinks
> ----------------------------------------
>
>                 Key: STORM-2038
>                 URL: https://issues.apache.org/jira/browse/STORM-2038
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-core
>    Affects Versions: 1.0.1
>         Environment: Any windows
>            Reporter: Paul Milliken
>            Assignee: Robert Joseph Evans
>              Labels: symlink, windows
>             Fix For: 2.0.0, 1.1.0, 1.0.4
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As of Storm 1.0 and above, some functionality (such as the worker-artifacts 
> directory) require the use of symlinks. On Windows platforms, this requires 
> that Storm either be run as an administrator or that certain group policy 
> settings are changed.
> In locked-down environments, both of these solutions are not suitable.
> Where possible, an alternative option should be provided to the use of 
> symlinks. For example, it may be possible to create additional copies of the 
> worker artifacts directory for each worker (possibly inefficient) or provide 
> the workers with the canonical path to the real directory.
> See the [brief 
> discussion|http://mail-archives.apache.org/mod_mbox/storm-dev/201608.mbox/%3C1293850887.13165119.1471022901569.JavaMail.yahoo%40mail.yahoo.com%3E]
>  on the mailing list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to