Hi Rajesh, I'd suggest to consider moving some queries over to Search API (https://cloud.google.com/appengine/docs/java/search/). For example, we use the custom datastore indexes (indices) primarily only for queries which have strong consistency requirements.
After we adopted this approach of focusing all “non-strict” queries to Search API, our custom index count stopped increasing quite effectively. As an added bonus, you also gain the much more versatile query capability of the Search API. And save the trouble of keeping track what kind of queries need to be supported by custom indices. Cheers, Janne, Swap.com On Thursday, March 17, 2016 at 2:03:05 PM UTC+2, Rajesh Gupta wrote: > > Hi, > We are using java appengine. We have already using 160 indexes. > > We plan to expand further with more functionality, but we will hit the 200 > index limit. > Our current architecture is servlets/jsp, with several GWT modules. > > What are my architecture options to add more functionality, with out > hitting the 200 index limit. > Can I use another new appid, and do the remote-api from the serverside > java code? > > Rajesh > *www.VeersoftSolutions.com <http://www.VeersoftSolutions.com>* > *www.AccountingGuru.net <http://www.AccountingGuru.net>* > *Accounting/Inventory/Orders on Google Cloud Platform and Mobile* > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/23f037e4-f90f-4ff7-ac04-bb123642d509%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
