--
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.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
I think your problem is similar to the mine.http://groups.google.com/group/google-appengine-java/browse_thread/thread/1ace5bd8658d89d/a62d0b3f2b3c4e74#a62d0b3f2b3c4e74
Ikai, please, can explain us how many cost in terms of write ops, should us expect for updating indexed list property adding X items to the list?
Iván,2012/1/6 Iván Rodríguez <ivan....@gmail.com>I think your problem is similar to the mine.http://groups.google.com/group/google-appengine-java/browse_thread/thread/1ace5bd8658d89d/a62d0b3f2b3c4e74#a62d0b3f2b3c4e74
Ikai, please, can explain us how many cost in terms of write ops, should us expect for updating indexed list property adding X items to the list?This page can help you work out the costs for your particular entities and indexes:E.g., it details the costs for the different datastore operations given an entity's properties and indexes.
A rebuild of an index is likely much cheaper in cost than updating one for each write.
-Wendel
This shouldn't help. Re-puting an entity won't cause index updates if
the indexed values don't change. The "relation index entity" pattern
is only useful when you have very large #s of index items (many
thousands). You wouldn't want to do it for 20 short strings.
Jeff