[jira] [Commented] (STORM-650) Storm-Kafka Refactoring and Improvements

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on STORM-650:
--------------------------------------

Github user d2r commented on the pull request:

    https://github.com/apache/storm/pull/406#issuecomment-111192307
  
    > Is it better to open separate JIRA issue or this pull request is considered as part of subjects discussed in STORM-650?
    
    @ogorun  I am sorry I did not see the notification for you comment earlier.  Yes, I think the place to discuss this is STORM-650.  We might ask on STORM-650 whether we should add a new JIRA Issue for this to the STORM-650 epic.  We might ask on STORM-650 whether we should add a new JIRA Issue for this to the STORM-650 epic.  So far, I am not sure this specific issue is addressed in STORM-650, and it seems some kafka API changes are coming as well.


> Storm-Kafka Refactoring and Improvements
> ----------------------------------------
>
>                 Key: STORM-650
>                 URL: https://issues.apache.org/jira/browse/STORM-650
>             Project: Apache Storm
>          Issue Type: Epic
>          Components: storm-kafka
>            Reporter: P. Taylor Goetz
>
> This is intended to be a parent/umbrella JIRA covering a number of efforts/suggestions aimed at improving the storm-kafka module. The goal is to facilitate communication and collaboration by providing a central point for discussion and coordination.
> The first phase should be to identify and agree upon a list of high-level points we would like to address. Once that is complete, we can move on to implementation/design discussions, followed by an implementation plan, division of labor, etc.
> A non-exhaustive, initial list of items follows. New/additional thoughts can be proposed in the comments.
> * Improve API for Specifying the Kafka Starting point
> Configuring the kafka spout's starting position (e.g. forceFromStart=true) is a common source of confusion. This should be refactored to provide an easy to understand, unambiguous API for configuring this property.
> * Use Kafka APIs Instead of Internal ZK Metadata (STORM-590)
> Currently the Kafka spout relies on reading Kafka's internal metadata from zookeeper. This should be refactored to use the Kafka Consumer API to protect against changes to the internal metadata format stored in ZK.
> * Improve Error Handling
> There are a number of failure scenarios with the kafka spout that users may want to react to differently based on their use case. Add a failure handler API that allows users to implement and/or plug in alternative failure handling implementations. It is assumed that default (sane) implementations would be included and configured by default.
> * Configuration/General Refactoring (BrokerHosts, etc.) (STORM-631)
> (need to flesh this out better) Reduce unnecessary marker interfaces/"instance of" checks. Unify configuration of core storm/trident spout implementations.
> * Kafka Spout doesn't pick up from the beginning of the queue unless forceFromStart specified (STORM-563)
> Discussion Items:
> * How important is backward compatibility?



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