You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gearpump.apache.org by "Kam Kasravi (JIRA)" <ji...@apache.org> on 2016/05/13 15:27:12 UTC

[jira] [Assigned] (GEARPUMP-119) Life Cycle of APP

     [ https://issues.apache.org/jira/browse/GEARPUMP-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kam Kasravi reassigned GEARPUMP-119:
------------------------------------

    Assignee: Kam Kasravi

> Life Cycle of APP
> -----------------
>
>                 Key: GEARPUMP-119
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-119
>             Project: Apache Gearpump
>          Issue Type: New Feature
>          Components: all
>            Reporter: Qi Shu
>            Assignee: Kam Kasravi
>
> Now app in Gearpump can only start and kill, it means if I want to update my app due to business logic change, I have to kill app, when this app start again and will become a new app(can' t share the offset before), so if the replayable source, such as kafka, has enormous messages, it can use a long time to reach the offset. The suggestion is that app may have a life cycle: start, stop, drop.



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