Hello,
On Wed, May 22, 2013 at 10:57 AM, kzhang <[email protected]> wrote: > Update -- we found the issue. There were some post requests coming in from > a > form, obviously not using image content type. We tried: > > curl -v -s -o/dev/null http://xxxxxx:8098/riak/45/21601_7803328_3.jpg --> > Fails > curl -v -s -o/dev/null -H "Accept: image/*" > http://xxxxxxx:8098/riak/45/21601_7803328_3.jpg --> Works > > my question though -- is the same key 21601_7803328_3 associated with > different values of different content types? We set in our config: > > > {allow_mult,false}, > {last_write_wins,true}, > > > I'd imagine one would overwrite the other, depending on which one comes in > late? > > Correct. With lww = true, the vector clocks will be ignored and the most-recent timestamp will win. Is this not what you're seeing? Mark > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/0-byte-images-saved-to-riak-cluster-tp4027932p4027945.html > Sent from the Riak Users mailing list archive at Nabble.com. > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
