Wow, that's a pretty big question. IMO, it depends upon what you're doing with your data. Personally, I'm storing up to 4 different "versions" of the same data in Riak, each version is optimized for different types of analytical operations.
That's probably not ideal for everybody. Heck, storing 4 copies of my data isn't even optimal for me from a storage perspective - but it does help optimize performance of different queries. I care more about that than disk or memory. On Tue, Sep 18, 2012 at 5:55 PM, Allen Johnson <akjohnso...@gmail.com>wrote: > Hey everyone, > > I'm beginning to experiment with Riak and I'm trying to better > understand how to model my data. One question I have at the moment is > how to evolve my data with a data store such as Riak? I know that > it's schema-less and that I can add new fields as needed but I'm > thinking more about the existing documents. > > For example, say hypothetically, that I have a fairly successful > riak-based app. As the application code continues to evolve over > several versions I begin to find a "better" way to model my data. By > this time I have already stored many, many documents. What is the > appropriate path here? Do I version my documents with metadata and > rely on my application code to continue to deal with old-style > documents -- or do I perform some sort of bulk transformation on these > existing documents? > > Thanks, > Allen > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > -- *Pinney H. Colton* *Bitwise Data, LLC* +1.763.220.0793 (o) +1.651.492.0152 (m) http://www.bitwisedata.com
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
