[
https://issues.apache.org/jira/browse/KAFKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147590#comment-15147590
]
Jason Gustafson commented on KAFKA-3093:
----------------------------------------
[~jinxing6...@126.com] I should have a patch available later today so it'd be
great if you could help review. For this ticket, I haven't tried to implement
any failure handling other than exposing the failure through the API. I
definitely think it would make sense for Connect to implement failure policies
(such as rolling back and restarting), but maybe we can do that in a separate
JIRA?
> Keep track of connector and task status info, expose it via the REST API
> ------------------------------------------------------------------------
>
> Key: KAFKA-3093
> URL: https://issues.apache.org/jira/browse/KAFKA-3093
> Project: Kafka
> Issue Type: Improvement
> Components: copycat
> Reporter: jin xing
> Assignee: Jason Gustafson
>
> Relate to KAFKA-3054;
> We should keep track of the status of connector and task during their
> startup, execution, and handle exceptions thrown by connector and task;
> Users should be able to fetch these informations by REST API and send some
> necessary commands(reconfiguring, restarting, pausing, unpausing) to
> connectors and tasks by REST API;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
