There’ll still be the need of a version vector, yes. Any advice/contribution on optimisations there greatly appreciated, thanks.
On 17 May 2016, at 09:05, Sargun Dhillon <sar...@sargun.me> wrote: > Is the plan to keep using riak_dt_vclock? If so, I might contribute > some optimizations for large numbers of actor entries (1000s). > > On Thu, Apr 28, 2016 at 12:55 AM, Russell Brown <russell.br...@me.com> wrote: >> Hi, >> Riak DT[1] is in need of some love. I know that some of you on this list >> (Sargun, are you here? Heinz?) have expressed opinions on the work that >> needs doing. Here is my short list, I would love to hear opinions on >> priority, and any additions to this list: >> >> 1. merger smaller map branch >> 2. deltas >> 3. new data types (we have a range register and some and >> Multi-Value-Register to add, any more?) >> 4. Internal state as records or maps (but not these messy tuples) >> 5. update to rebar3 >> 6. update to latest erlang >> >> I’m pretty sure there is plenty more. Would greatly appreciate your feedback. >> >> Many thanks >> >> Russell >> >> [1] https://github.com/basho/riak_dt/ >> _______________________________________________ >> riak-users mailing list >> riak-users@lists.basho.com >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
