[
https://issues.apache.org/jira/browse/ACCUMULO-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328125#comment-14328125
]
Christopher Tubbs commented on ACCUMULO-3594:
---------------------------------------------
I have not tried avro, but I've been a little disillusioned by thrift's lack of
regression testing (like the one inspiring THRIFT-2173) and some questionable
decisions (like the one identified in ACCUMULO-2950). With both thrift and
protocol buffers, there's also the frustration of performing pre-build steps
for code generation which is a bit unfriendly (especially in maven, and
especially when reliant on a particular version of the compiler).
However, I don't have a strong preference.
> Consider message replacement for Writable classes internally
> ------------------------------------------------------------
>
> Key: ACCUMULO-3594
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3594
> Project: Accumulo
> Issue Type: Sub-task
> Reporter: Josh Elser
> Fix For: 1.7.0
>
>
> We have a number of writable classes, some of which are non-trivial and
> serialized in tables or files:
> * {{org.apache.accumulo.core.tabletserver.log.LogEntry}}
> * {{org.apache.accumulo.core.metadata.schema.DataFileValue}}
> * {{org.apache.accumulo.server.master.state.TServerInstance}}
> Consider converting this (and possibly others) to better message classes to
> easily add more functionality in the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
