Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v1.0.0
    • Fix Version/s: v1.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Create client SDK. Creating as sub-task of Client SDK with Failover capability.

      There are no Sub-Tasks for this issue.

        Activity

        Hide
        Arvind Prabhakar added a comment -

        Subtasks complete. Thanks Mike and Hari!

        Show
        Arvind Prabhakar added a comment - Subtasks complete. Thanks Mike and Hari!
        Hide
        E. Sammer added a comment -

        If it helps, my intention was to extract the Avro stuff from flume-ng-core into flume-ng-avro that contained the source, sink, IDL, and generated protocol and build a thin client around that. Clients should probably use a facade that simplifies connection configuration and management (think of things like what this will look like when we add TLS). Avro RPC is also extremely heavy even with Netty rather than HTTP so the ability to batch is critical as well. Anyway, just thoughts...

        Show
        E. Sammer added a comment - If it helps, my intention was to extract the Avro stuff from flume-ng-core into flume-ng-avro that contained the source, sink, IDL, and generated protocol and build a thin client around that. Clients should probably use a facade that simplifies connection configuration and management (think of things like what this will look like when we add TLS). Avro RPC is also extremely heavy even with Netty rather than HTTP so the ability to batch is critical as well. Anyway, just thoughts...
        Hide
        Mike Percy added a comment -

        OK sounds good guys will do!

        Show
        Mike Percy added a comment - OK sounds good guys will do!
        Hide
        Arvind Prabhakar added a comment -

        +1 on Prasad's suggestion. Lets make this as the top-level Jira with failover being a subtask of it along with other things it needs to do.

        Show
        Arvind Prabhakar added a comment - +1 on Prasad's suggestion. Lets make this as the top-level Jira with failover being a subtask of it along with other things it needs to do.
        Hide
        Prasad Mujumdar added a comment -

        In my opinion, the client SDK has more purposes than just to facilitate HA. For example, it should implement interfaces for handling Flume's avro format. The custom clients need to create flume events and customer terminal repositories want to extract data from Flume event. Currently the Avro RPC is hardwired into the Flume 'application' and avro source/sink. Ideally it should be part of this client SDK library so that custome client and repositories can be developed on top of it.
        Further the SDK can also include interfaces that introspects event headers for customer decorators, once that functionality is implemented.

        Perhaps this FLUME-988 : Client SDK should be an umbrella Jira, with failover and others as sub-task ...

        Show
        Prasad Mujumdar added a comment - In my opinion, the client SDK has more purposes than just to facilitate HA. For example, it should implement interfaces for handling Flume's avro format. The custom clients need to create flume events and customer terminal repositories want to extract data from Flume event. Currently the Avro RPC is hardwired into the Flume 'application' and avro source/sink. Ideally it should be part of this client SDK library so that custome client and repositories can be developed on top of it. Further the SDK can also include interfaces that introspects event headers for customer decorators, once that functionality is implemented. Perhaps this FLUME-988 : Client SDK should be an umbrella Jira, with failover and others as sub-task ...

          People

          • Assignee:
            Unassigned
            Reporter:
            Mike Percy
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development