Hi Tonny,
The query you describe below can be satisfied using the built in
indexes and a merge join. Merge join queries, however, can be a little
less efficient than using a composite index. You can reduce timeouts
and improve query efficiency by creating a composite index for this
query like
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
erwtwertwert
On Jul 18, 1:22 pm, Tonny mezz...@gmail.com wrote:
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
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
