[
https://issues.apache.org/jira/browse/HBASE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723853#action_12723853
]
stack commented on HBASE-1577:
------------------------------
Experimenting and chatting w/ Ryan, he suggested putting kv into value too.
Then when new kv that has an extant key but whose value is different, the key
object in Map stays same but it looks like the 'new' kv goes in as value. This
will do for us. Just need to do bunch of work making sure we always get from
value, not from key. Also, need to explain it and be careful with how we
update HeapSize -- if different value, then be sure to add differences. Could
become significant.
> Move memcache to ConcurrentSkipListMap from ConcurrentSkipListSet
> -----------------------------------------------------------------
>
> Key: HBASE-1577
> URL: https://issues.apache.org/jira/browse/HBASE-1577
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Fix For: 0.20.0
>
> Attachments: 1577-v2.patch, set2map.patch
>
>
> The CSLM will replace old entry with a new when you put. The CSLS will NOT
> replace if existent key making for a test, and if present, remove semantic
> which to be safe needs synchronizing (Replacement is a Ryan Rawson
> suggestion).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
