Details
Description
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?
Attachments
Attachments
Issue Links
- is related to
-
ACCUMULO-143 Accumulo Hive
- Resolved
- relates to
-
ACCUMULO-210 create packages that enable accumulo features on the given node
- Resolved
1.
|
Exclude thrift generated classes from javadoc generation | Resolved | Christopher Tubbs | |
2.
|
Consolidate Thrift connection helper classes | Resolved | Unassigned |