accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3594) Consider message replacement for Writable classes internally
Date Fri, 20 Feb 2015 20:03:13 GMT

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

Sean Busbey commented on ACCUMULO-3594:
---------------------------------------

If we went with Avro we could use their maven plugin to generate specific classes for serialization
without needing an external compiler. Alternatively, we could rely on Avro's generic serialization
implementation (but it's a little slower).

Avro also has good reputation for being "safe", largely because they do regression testing
and favor stability over time. (the disadvantage of this is that they can be a little slow
in adopting new features, but participation in the community can help mitigate that.)

> 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)

Mime
View raw message