[
https://issues.apache.org/jira/browse/S4-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556331#comment-13556331
]
Matthieu Morel commented on S4-59:
----------------------------------
Submitted a patch in branch S4-59, commit [d3b7c30]
The idea is to rethink the way we configure nodes and apps.
Instead of independently configuring S4 nodes, and having to modify their
classpath - not in a nice way - in order to add custom modules, I propose to:
* start S4 nodes with only the bare minimum, i.e. the mechanism to pick
partitions and register on the cluster
* specify everything along with the application:
** custom modules, and a way to fetch relevant code if necessary
** application class, and a way to fetch relevant code and dependencies if
necessary
>From a user point of view, starting an app on a cluster involves:
* configuring cluster in zookeeper (number of partitions)
* starting s4 nodes
* deploying application, including custom platform config (modules)
The nodes will automatically fetch everything necessary for running the app
with the expected configuration
> Resource loading from the S4 node classpath
> -------------------------------------------
>
> Key: S4-59
> URL: https://issues.apache.org/jira/browse/S4-59
> Project: Apache S4
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Daniel Gómez Ferro
> Fix For: 0.6
>
>
> There should be a way to add custom files to the application's Classpath.
> This is useful to configure the logging backend, for example.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
