You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/01/29 17:21:13 UTC

[jira] [Commented] (ACCUMULO-1003) what is the point of SecuritySerDe?

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

John Vines commented on ACCUMULO-1003:
--------------------------------------

This was so token implementations could opt for faster serialization methods. With every single call resulting in deserialization (and having been bitten by this on another project), I wanted to provide a mechanism to be sure that it wouldn't gum things up. Must it appears that this is a non-issue from comments being made.
                
> 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