reverri at gmail.com
Mon Apr 26 14:21:57 EDT 2010
I've started storing data encoded as JSON in order to allow access through
the REST API. This adds a bit of overhead in Erlang but allows the data to
be accessed from other clients such as http://github.com/johnthethird/Briak
On Mon, Apr 26, 2010 at 6:10 AM, Sean Cribbs <sean at basho.com> wrote:
> Yes, the primary weakness of records would be upgrading them. You could do
> it with a map-reduce job, but it would be better in general to use a more
> fluid data structure.
> Whether you choose proplists or dicts will depend on how many properties
> you need. Dicts become more efficient when the number of keys grows large,
> but for most cases a proplist or orddict would be good enough.
> Sean Cribbs <sean at basho.com>
> Developer Advocate
> Basho Technologies, Inc.
> On Apr 25, 2010, at 11:25 PM, David Weldon wrote:
> > I assume there is an inherent danger in writing erlang records to riak
> > - If the record definition changes, you can no longer read the stored
> > data back into the new record type. Is this assumption correct? If so,
> > do people just always use proplists, dicts, etc. when storing complex
> > values?
> > _______________________________________________
> > riak-users mailing list
> > riak-users at lists.basho.com
> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users