Exploding explosive indexes

[Harshal Patil]

Running into famous exploding indexes application, causing writes to shot through the roof. 

In this talk - http://code.google.com/events/io/2010/sessions/next-gen-queries-appengine.html

- you guys mentioned about solving this issue. I know asking for timelines to Google is of no use, but all I want to convey is 'do it ASAP' . Another feature that we are eagerly want to have is 'NOT' in gqlquery.

Hope this doesn't fall on deaf ears. 

Harshal 

[Ikai L (Google)]

Yep, it's being worked on. Perhaps you can describe what you are trying to achieve? There may be an alternate solution that doesn't involve multiple List properties on an entity.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Ikai Lan 
Developer Programs Engineer, Google App Engine

Blog: http://googleappengine.blogspot.com 

Twitter: http://twitter.com/app_engine

Reddit: http://www.reddit.com/r/appengine

[Carbon Sink]

Ikai:

We are also running into this exploding index issue.

Here's our situation: records on entity 'Report' are tagged with
multiple keywords ('tags') like: 'music', 'event', 'downtown',
'zz_top', 'concert', 'g_arena', 'september', '2010'. People might
search for events downtown in September like this:

city.domain.com/tags/event/september/2010/downtown

So we are using a 'tags = db.ListProperty(basestring, required=True,
validator=are_valid_tags)' in our table with queries like:

reports = db.Query(Report).filter('tags =', subdomain)
for tag in tags:
reports = reports.filter('tags =', tag)
reports = reports.order('-approval_time').fetch(int(25))

Advice and/or insight would be much appreciated!

On Jun 4, 9:32 am, "Ikai L (Google)" <ika...@google.com> wrote:
> Yep, it's being worked on. Perhaps you can describe what you are trying to
> achieve? There may be an alternate solution that doesn't involve multiple
> List properties on an entity.
>
>
>
> On Thu, Jun 3, 2010 at 10:15 PM, Harshal <p.hars...@gmail.com> wrote:
> > Running into famous exploding indexes application, causing writes to shot
> > through the roof.
>
> > In this talk -

> >http://code.google.com/events/io/2010/sessions/next-gen-queries-appen...

> > - you guys mentioned about solving this issue. I know asking for timelines
> > to Google is of no use, but all I want to convey is 'do it ASAP' . Another
> > feature that we are eagerly want to have is 'NOT' in gqlquery.
>
> > Hope this doesn't fall on deaf ears.
>
> > Harshal
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-appengi...@googlegroups.com<google-appengine%2Bunsu...@googlegroups.com>
> > .