If search>datastore was true, I would definitely do that, search is more powerful However, it's unclear what are search's limits, first of all there is the 250gb index limit, even if that was elevated it's unclear whether it can perform as good as datastore There is also the cost issue, even if it performed as good as datastore, it could result in a huge increase in costs
I'm using search api with actual text search, and it replicates the functionality of the original sort orders/views pretty good, however there are the concerns I mentioned On Saturday, October 19, 2013 11:47:34 PM UTC+3, Nick wrote: > > More than one or two sort orders will drastically increase the number of > indexes you need to create, particularly if you're using range queries too. > In the scenario you've described I would highly recommend duplicating your > data into the SearchService and running searches on that. > This will allow you to just use keys/ids for datastore lookups. > > I usually index a couple of basic fields for operational queries through > the admin console. > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
