I just came up with this last night, and have only done limited
testing. I can guess what you mean by the exploding index problem,
but are there any particulars you can give? Does the exploding index
problem impact mostly total data storage, time to index, or
performance on the GQL queries? Or some combination of the above?
I definitely mean to do some testing, but my assumption--tell me if
I'm on the wrong track--is that the indexing is primarily a challenge
when adding new data, and maybe in data storage. But if I'm right
here, then it's not too much of an issue for me, as I imagine that my
app will mostly see incremental additions of data to be indexed; I
won't be doing bulk loads which I can imagine could bog things down
significantly.
Any links to other threads on this issue would be appreciated.
-Ben ("readyassist")
On Sep 9, 8:52 am, uprise78 <[EMAIL PROTECTED]> wrote:
> Won't having a list property like that get you the exploding index
> problem? Have you done any testing with a large subset of data?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
