I recently watched a Google I/O Talk regarding exploding indexes, and
realized that the application that I am currently developing has
queries that are susceptible to this problem. Try as I might, I can't
think of a good way to resolve my problem, so I was hoping to get some
input.
My database model is as follows:
class Entries(db.Model):
campaigns = db.ListProperty(db.Key)
owners = db.ListProperty(db.Key)
owners_saved = db.ListProperty(db.Key)
owners_unsaved = db.ListProperty(db.Key)
parent_entries = db.StringListProperty()
entry = db.StringProperty()
stat1 = db.IntegerProperty(default = 0)
stat2 = db.FloatProperty()
stat3 = db.FloatProperty()
stat3_categories= db.StringListProperty()
I am attempting to do queries such as:
SELECT * FROM Entries WHERE campaigns=:1 and stat3_categories=:2 and
owners_saved=:3 ORDER BY stat1
The problem is rooted in the fact that length of the campaigns and
owners_saved list can potentially grow into the hundreds and
stat3_categories can be up to 40 elements long.
I have read other threads in relation to solutions for this problem.
One solution that comes up is to remove the sort from the query.
However, each query results in thousands of results, and I am only
retrieving 10 at a time (and displaying the results in paged format).
Are there other ideas on how to resolve this type of exploding index
issue?
--
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.
