[
https://issues.apache.org/jira/browse/ACCUMULO-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566568#comment-13566568
]
Eric Newton commented on ACCUMULO-1003:
---------------------------------------
I understand that it's to provide alternative serialization methods, but we
already have the extra level of indirection in the SecurityToken. If I want
faster/better serialization, can't I just use a new class? And since hadoop
already has a mechanism for substituting different classes for Writables, we
can leverage that infrastructure for future improvements. For example, we've
replaced the implementation of the objects written to the WAL between releases
by updating the classes and providing the Hadoop library with the translation.
This just looks overly complex. That's fine if it has a point.
> what is the point of SecuritySerDe?
> -----------------------------------
>
> Key: ACCUMULO-1003
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1003
> Project: Accumulo
> Issue Type: Sub-task
> Components: master, tserver
> Reporter: Eric Newton
> Assignee: John Vines
> Fix For: 1.5.0
>
>
> What is the point of the factory method getSerDe() (which, BTW is an awful
> name)? Why not just make SecurityToken Writable?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
