accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3594) Consider message replacement for Writable classes internally
Date Thu, 26 Feb 2015 22:30:05 GMT

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

Christopher Tubbs commented on ACCUMULO-3594:
---------------------------------------------

bq. we'll just have to make sure we recompile things after we update

It'd be nice if this was added as a profile in the build, and required in the release profile,
similar to the thrift profile we have today. Last I checked, our script to regenerate our
proto files needed to be manually executed (and it's not entirely obvious that these are generated
files in the first place; at least, it wasn't obvious to me when I was looking at cleaning
up the -Xlint:all compiler warnings).

> 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