[jira] [Commented] (STORM-117) Storm should provide client library

["Simon Cooper (JIRA)" <ji...@apache.org>]

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

Simon Cooper commented on STORM-117:
------------------------------------

I would like to see this also. Any programs/libraries communicating with nimbus and deploying topologies currently have to ship with the entire storm runtime, which bloats the library quite a bit.

> Storm should provide client library
> -----------------------------------
>
>                 Key: STORM-117
>                 URL: https://issues.apache.org/jira/browse/STORM-117
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: Daniel Cruver
>
> Developers that would like to use distributed services such as Storm should have client libraries that allow users to deploy applications (Topologies) and send requests to these application without requiring dependencies only required by the services. 
> Definitions:
> Service Environment - Storm Nimbus, DRPC and, workers
> Client Environment - Standalone JVM, Web Application etc.
> One example of this is hadoop-client. Before it was created user would use hadoop-core and they would be force to include or manually exclude servlet artifacts and other such artifacts that may cause classpath issues in the client's environment. This will cut down on confusion to new storm users that are unfamiliar with the details of storm and logging frameworks or user integrate storm into existing applications.
> One such example is storm now includes Logback-classic, when user adds this to a project that uses slf4j-API it causes their logging system to break. This happen to our project until we manually excluded Logback. In our environment like others uses log4j for logging.  Yes Logback is an improvement over log4j but you can't expect others to change their standard logging framework because of one external dependency.  Also there are newer alternatives like log4j 2 and jboss logging that will compete to be the upgrade path for those that would like to update.
> To start off with I do not expect storm to allow users to change the logging framework used for client code while executing in the context of storm workers just the code run from the requesting application. Note allowing system administrators to change the logging framework would be easy since you are using slf4j.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)