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

Wang, Gang commented on MNEMONIC-104:
-------------------------------------

Yes, the Durable Map is expected to have generic key as well as generic value 
as Durable list does. the user could retrieve the durable map data back without 
schema in place.
Regarding the sync, it depends on the underlying memory service (e.g. supports 
flush when closed, flush on demand or transaction), so far, It should guarantee 
to flush data when its underlying memory service is closed. the nvml-pmemobj 
supports transnational operations, we would plan to adopt this feature into 
Mnemonic later on but the major concern seems to be about the overhead caused 
by the copy operation of this transaction feature for the applications of big 
data processing.
For the replication, I think It could be possible for a DFS to replicate the 
partitions of Mnemonic memory service outputs.  
If finer granularity replication of Mnemonic structures needed, I think we have 
to make memory service support the replication feature as well.


> Create a Durable Map
> --------------------
>
>                 Key: MNEMONIC-104
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-104
>             Project: Mnemonic
>          Issue Type: New Feature
>          Components: Collection
>    Affects Versions: 0.4.0-incubating
>            Reporter: Wang, Gang
>            Assignee: Johnu George
>             Fix For: 0.5.0-incubating
>
>
> A durable map (DM) would be a general key structure of Mnemonic collections. 
> the durable map should be able to be recovered from any kind of memory 
> services e.g. volatile/non-volatile without doing heavily serDe operations, 
> in addition, DM is required to load its data lazily to amortize memory/IO/CPU 
> consumption. at the first stage, the DM could be implemented using most 
> feasible approach, e.g. Hashmap, and not necessary to comply with the 
> interface of Java Map, but the Key/Value of DM should support generic types 
> as Durable list does. 
> the DM aims to manage huge amount of mutable key-value datasets, so the 
> design of Durable map should be flexible enough as possible to accommandate 
> future optimizations. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to