Paul, yes. Whenever you update an entity, any property that is not explicitly marked as unindexed will generate 2 index writes. Any update to that property will cause 2 writes to delete the old indexes and 2 writes to write the new ones. The indexes are used in queries, e.g.:
select from user where name='bob' If you don't have the 'name' property indexed, you won't be able to run that query. If you never run a query against a property, mark it as unindexed. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Thu, Dec 22, 2011 at 12:02 AM, Paul <pgronkiew...@gmail.com> wrote: > Also, another question: > > I don't even have datastore-indexes.xml generated, should I even have > any index write ops possible without it? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
