Got another problem.
There is a "Ticket" kind in my datastore. I want to run a search query on a
several fields, e.g.: { active, technicianKey, vip, dueDate } and order
results by {techPriorityLevel} field (ascending).
According to article you recommended, it's not necessary for me to define a
composite index for all those fields since I already have indexes for all
pairs "search field, order field", like
<datastore-index kind="Ticket" ancestor="false" source="manual">
<property name="vip" direction="asc"/>
<property name="techPriorityLevel" direction="asc"/>
</datastore-index>
and so on.
However, instead of performing a zigzag merge join, datastore throws
a DatastoreNeedIndexException stating that I should explicitly define a
composite index like
<datastore-index kind="Ticket" ancestor="false" source="manual">
<property name="active" direction="asc"/>
<property name="technicianKey" direction="asc"/>
<property name="vip" direction="asc"/>
<property name="dueDate" direction="asc"/>
<property name="techPriorityLevel" direction="asc"/>
</datastore-index>
Currently experiencing this behavior on development server (AppEngine SDK
1.7.0, Eclipse 3.7.1, using Google plugin for Eclipse).
Is there something I'm missing or doing wrong? Maybe this will work
correctly only with real datastore, not local development server? (Still
can't check that out because of those 220 stuck indices in datastore.)
Thanks in advance,
Oleg
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/JjnskSfa_4YJ.
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.
