[
https://issues.apache.org/jira/browse/S4-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Morel updated S4-10:
-----------------------------
Fix Version/s: (was: 0.5)
0.6
Rescheduling for a later release.
We could even close it. As Flavio mentioned, we are probably already good with
what we currently have. Otherwise the definition of the work becomes too
abstract and I feel it's too hard to decide upon a completion state.
> Dynamic s4 cluster management:S4 as a service
> ---------------------------------------------
>
> Key: S4-10
> URL: https://issues.apache.org/jira/browse/S4-10
> Project: Apache S4
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: kishore gopalakrishna
> Fix For: 0.6
>
>
> One of the features that we will definitely need to make S4 as a service is
> being able to do following operations without bringing down the cluster
> * Deploy/undeploy applications. High level goal is to be able to provide a
> uri which will point to the application jar and deploy it to all nodes in s4
> cluster.
> * Configure/add new stream into the system, this will basically contain how
> is the stream partitioned. Currently each stream is partitioned based on
> number of nodes but this may not always be desirable.
> * Configure/Add Processing Elements. Basically attach a PE to a stream
> without writing any custom code.
> * Add query, one should be able to submit a query for common tasks like
> count/avg/min/max/. This can eventually be expanded to support UDF.
> Will use this as a high level JIRA to make S4 as a service. Only features
> will be added to this JIRA. For each feature we can create child JIRA
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
