Thanks for the reply, I saw the video too. I'm just a bit surprised
that this actually happens a couple of time a day -and though - Im
must be doing something wrong. Guess better starting handling those
exceptions...

On 19 Jul., 01:40, djidjadji <djidja...@gmail.com> wrote:
> If my memory is correct Bret Slatkin talked about these type of
> queries in a I/O 2009 presentation. You don't need a composite index
> for this type of query. It uses the single property indexes.
>
> You have to write your code to deal with TimeOut Exceptions.
> You can retry the read when you get a TimeOut.
> This often helps but there are times that even 2 retries fail.
> You have to write code to deal with this situation.
> The TimeOut Exceptions happen for a very small percentage of Bigtable
> operations.
>
> 2009/7/18 Tonny <mezz...@gmail.com>:
>
>
>
>
>
> > Hello
>
> > I have a simple query like this: MyEntity.all().filter('prop1 =',
> > value1).filter('prop2 =', value2).get()
>
> > Every now and then it times out. To me it looks simply enough, but as
> > I started digging into the issue i came to doubt that I had the proper
> > indexes in place. In a relational database I would have made a
> > composite index for prop1 and prop2, but I can't find anything in the
> > app engine documentation about such an index. Rather I think it
> > suggests that the default indexes are sufficient for handling fetches
> > filtered by two attributes.
>
> > Does anybody know if default indexes are just as efficient as a
> > composite index, would the composite index be used at all?
>
> > Cheers
> > Tonny
--~--~---------~--~----~------------~-------~--~----~
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-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to