[jira] [Updated] (ACCUMULO-756) Thrift API should be removed and abstracted

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs updated ACCUMULO-756:
---------------------------------------
    Priority: Major  (was: Critical)

> Thrift API should be removed and abstracted
> -------------------------------------------
>
>                 Key: ACCUMULO-756
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-756
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: build, rpc
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Major
>              Labels: api, module, rpc, thrift
>             Fix For: 2.0.0
>
>         Attachments: ACCUMULO-756.patch
>
>
> The thrift API for communication between components should be abstracted out and made more generic, so we can plug in different communications mechanisms. The thrift code generation and the generated code should be moved to a specific implementation of this abstraction, and put in a separate sub-module.
> This can help with:
>  1. Making full mocking support easier (ACCUMULO-14) with an in-process "RPC" implementation.
>  2. Testing alternative protocols, like Avro, Protocol Buffers, SSL, etc.
>  3. Minimizing dependencies and isolating thrift generated code from code that is maintained (ACCUMULO-493).
>  4. Wire compatibility (ACCUMULO-751).
>  5. More?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)