[
https://issues.apache.org/jira/browse/ACCUMULO-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339249#comment-14339249
]
Josh Elser commented on ACCUMULO-3594:
--------------------------------------
I stumbled onto https://code.google.com/p/protobuf/issues/detail?id=476 today
which aims at providing an upstream maven-protoc-plugin for use. Linking here
so I don't forget about it.
I was introduced HADOOP-9845 today. It outlines some concerns I had over
dealing with protobuf jar updates. Since we're packing our own, it should be
fine, we'll just have to make sure we recompile things after we update. It
would force any other protobuf classes (e.g. user combiners/iterators) to be
generated with the version that we use (unless some table/namespace context
classpath stuff is used). Some more food for thought.
> 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)
