I think, I may copy the contents of each message in the PlayerMessage model
to avoid having another lookup. I'll choose higher storage capacity over
10 calls to load each individual message.
On Wed, Sep 26, 2012 at 2:51 AM, Rune Skou Larsen wrote:
> On 25-09-2012 23:18, Charlie Bowman wrote:
On 25-09-2012 23:18, Charlie Bowman wrote:
Can I load 10 messages in 1 call? similar to a sql call "select * from
messages where id in (1,2,3,4,5,6,7,8)"
You can specify an array of keys as inputs to a MapReduce job.
http://wiki.basho.com/MapReduce-Implementation.html#Inputs
MR jobs can be slow
Sorry for the spam, I guess I'm hitting some keyboard shortcut thats
sending the message. let me try 1 more time.
Can I load 10 messages in 1 call? similar to a sql call "select * from
messages where id in (1,2,3,4,5,6,7,8)"
On Tue, Sep 25, 2012 at 2:17 PM, Charlie Bowman wrote:
> accidentally
accidentally hit enter before I finished the last question. The last
sentence was:
Can I load 10 messages in
On Tue, Sep 25, 2012 at 2:16 PM, Charlie Bowman wrote:
> You actually hit on several nuances regarding the app that I left out of
> the original email to keep things simple. I go a littl
You actually hit on several nuances regarding the app that I left out of
the original email to keep things simple. I go a little deeper now, and I
have a question regarding the link walking
"should make PlayerMessage PlayerMessages"
I agree, I was actually referencing my model name, which I alw
Looks good! A couple of observations:
The relation from PlayerMessage to Message introduces the possibility of
inconsistency by either dead references to Message or orphan Messages.
Thats managable - just an inconvinience.
If you need to read PlayerMessage and corresponding Messages in one go,
+riak list
My current plan is to use something very similar to your second idea (bulk
messages in 1 object). Here's my current idea, I would love to hear your
opinion on this! Sometimes a message will be sent to over 1M recipients, so
I think I'll store the message contents in its own model. My
The best data model always depends on the structure of data and the
access pattern. The natural access pattern for your messages is likely
lookup from two sides: sender and receiver. And you might need to
support message expiry too. This means that you need on-disk indeces if
you want more mess
I'm in the process of designing an in game messaging system that basically
replicates the same functionality of email all within the context of the
application. I do not have a ton of experience with true key/value db
stores so I'm looking to find a good resource for ideas on how to best
model thi
I have a category of data in my riak application that I can't figure out how to
model efficiently. For most of my data, inter-item relationships are relatively
compact, and stored solely for the purpose of being provided back to the user
as additional information transformed into api and view pa
10 matches
Mail list logo
