Github user erikdw commented on the pull request:
https://github.com/apache/storm/pull/822#issuecomment-163721659
@revans2 : good memory, my use-case is indeed storm-on-mesos. And in the
way my company deploys it, we leverage the `storm.log.dir` to force the logs to
be written into a known location where we can forward them to various
downstream log-indexing/storing services. That is the use case we want to be
supported *somehow*. I'm not particularly married to `storm.log.dir`, so your
proposal to have the `worker-artifacts` go to some other location seems
sufficient for my use case. I'll explicitly state that I would expect it to be
a knob that is configurable from within `storm.yaml`.
BTW, changing to a hierarchical layout from a flat style was concerning at
first blush, but on further reflection I believe it will work just fine. Our
tools for log-forwarding can use globs/wildcards so it should be ok.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
