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

stack commented on HBASE-20894:
-------------------------------

Added a suggestion (See  
[^0001-Write-the-CacheableDeserializerIdManager-index-into-.patch] ). It is 
incomplete. Missing is some serialization juggling (TODO). Patch removes an 
indirection that we have in naming BucketEntry deserializers. If we are 
breaking serialization -- i.e. moving from one serialization type to another -- 
this is an opportunity for simplifying this bit of cryptic code. Perhaps 
integrate this patch? I'll finish it up if wanted (This suggestion comes of an 
innocent [~mdrob] question asking what is UniqueIndexMap for?).

> Move BucketCache from java serialization to protobuf
> ----------------------------------------------------
>
>                 Key: HBASE-20894
>                 URL: https://issues.apache.org/jira/browse/HBASE-20894
>             Project: HBase
>          Issue Type: Task
>          Components: BucketCache
>    Affects Versions: 2.0.0
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: 
> 0001-Write-the-CacheableDeserializerIdManager-index-into-.patch, 
> HBASE-20894.WIP-2.patch, HBASE-20894.WIP.patch, HBASE-20894.master.001.patch, 
> HBASE-20894.master.002.patch, HBASE-20894.master.003.patch
>
>
> We should use a better serialization format instead of Java Serialization for 
> the BucketCache entry persistence.
> Suggested by Chris McCown, who does not appear to have a JIRA account.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to