You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2017/02/22 22:12:44 UTC
[jira] [Created] (GOSSIP-60) Clean up the shared/pernode/crdt API
data methods
Edward Capriolo created GOSSIP-60:
-------------------------------------
Summary: Clean up the shared/pernode/crdt API data methods
Key: GOSSIP-60
URL: https://issues.apache.org/jira/browse/GOSSIP-60
Project: Gossip
Issue Type: Improvement
Reporter: Edward Capriolo
Inside the code we are mutating nested concurrent maps and using resolution logic based on time stamps. There are some cases where we are not doing it correctly.
I have done this in other projects using looping.
https://github.com/edwardcapriolo/nibiru/blob/master/src/main/java/io/teknek/nibiru/engine/Memtable.java
And using a versioned approach with "garbage collection"
https://github.com/edwardcapriolo/nibiru/blob/master/src/main/java/io/teknek/nibiru/engine/VersionedMemtable.java
We should also remove the chained calls from GossipService. Users can simply use gossipService.getGossipmanager().put...
We should also give the users methods to call:
put (Long ts, long timeToLive, Object data)
instead of asking them to construct GossipDataMessages and send those along.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)