@Jason, you have to very careful about this change. Couple of years back, i had made similar change without doing complete homework as to where the columns are being used and ended up breaking the code in number of places. Since single column queries are only inside your code and if code base is large, there is potentially no way you can be sure about where all a particular column is being used. So, make is perfectly sure that you dont need the index before removing it.
Also, once the index is set to false, it is not clear, if you decided you need the index back, what is going to happen in that case. Will GAE rebuild the index? If yes, i dont think it shows up on the indexes page if it is being rebuilt. So you can be pretty much in the dark as to what is going on. On Sep 1, 1:04 pm, Jason Collins <jason.a.coll...@gmail.com> wrote: > "Just Datastore Writes alone is costing me more than before." > > We are seeing a massive, almost unexplainable, datastore write > operations number. > > Index writes count as a datastore write operation. I've recently > discovered (thanks Robert Kluin) that it's not just the indexes > mentioned in your index.yaml, but also the "per-attribute" indexes (2/ > attribute: asc, desc). > > Currently wading through many, many models to set indexed=False.... > > j > > On Aug 31, 6:45 pm, "Raymond C." <windz...@gmail.com> wrote: > > > > > > > > > Just Datastore Writes alone is costing me more than before. -- 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.
