Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

updated import

Browse Source
This commit is contained in:
boundedbuffer
2014-12-07 22:28:38 +00:00
parent 3d1cc76a05
commit f3f3c84c0f
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -2
View File
@@ -628,10 +628,12 @@ void putAll(File fromFile) throws IOException;
Its only the entries of your map that are exported, not the configuration of your map. So care
must be taken to populate the data in to a map of the correct Key/Value type and with enough
available entries. When importing data :
* entries that are in the map but not in the JSON file will remain untouched.
* entries that are in the map and in the JSON file will be updated.
* entries that are not in the map but are in the JSON file wil added.
* In other words importing data into a Chronicle Map works like `map.putAll(<JSON entries>)`.
* entries that are not in the map but are in the JSON file will be added.
In other words importing data into a Chronicle Map works like `map.putAll(<JSON entries>)`.
When Importing data if you are also writing to the map at the same time, the last update will win.
In other words a write lock is not held for the entire import process.