Google I/O 2011: Full Text Search
Why Stack Overflow recommends it
Stack Overflow users link it when asking about the App Engine Search API, especially the features it previewed such as geo search, datastore integration and transactions, and whether those features actually shipped.
Recommended by 0 people across 0 different months, 2011 to 2015.
What it is
A Google I/O 2011 session by Bo Majewski and Ged Ellis announcing the Full Text Search service for App Engine, built on Google's own search infrastructure. It covers the basic search API, briefly previews numeric, geo and date search, and shows how search ties into the datastore.
What people said
Cites themihai · 2011-06 · Stack Overflow · on “What is a Google AppEngine Instance?”
Is an instance a VM with a set of memory and a fixed amount of dedicated CPU power, memory etc or something else? Yes, exactly that it is. A VM with a set of memory and a fixed amount of dedicated CPU power. I can't remember how many instances a google server has but they said that in a I/O session. They also said what kind of servers google is using for App Engine ( quad core with some big amount of ram). Here it's the recording if I'm not wrong [this video]
Cites Bryce Cutt · 2011-08 · Stack Overflow · on “Indexes for google app engine data models”
I know it seems counter-intuitive but you can use a full-text search system that supports categories (properties/whatever) to do something like this as long as you are primarily using equality filters. There are ways to get inequality filters to work but they are often limited. The faceting features can be useful too. The upcoming Google Search API [this video] IndexTank is the service I currently use [LINK] EDIT: Yup, this is totally a hackish solution. The documents I am using it for are already in my search index and I am almost always also filtering on search terms.
Cites Janusz Skonieczny · 2012-05 · Stack Overflow · on “How to store lat-lon geolocation point in a document for GAE search?”
There where indications in the GoogleIO talk on Search API [this video] that we can do searches based on geolocation. I can't find an appropriate field [LINK] to store location info. How can I store geolocation info in the document [LINK] so I could issue queries based on distance from a particular GPS location?
Cites David Ward · 2012-08 · Stack Overflow · on “appengine objectify text search”
Maybe I am missing something but is there any way to use the new text search features as described in the 2011 presentation [this video] (approx. 30min mark) with Objectify, Entities, and Java? I realize it is an experimental release but the text search features that are present don't seem to cover the full extent they discussed in the presentation. I don't want to have to write my own code to manage the creation, updates to documents. But I don't currently see another way??
Cites Jens · 2014-02 · Stack Overflow · on “Does App Engine Search API support transactions?”
It is not too clear from the documentation if Search API operations can be part of a Datastore transaction. So can we expect the same ACID properties that we expect from Datastore operations in a transaction. And is a Document similar to an Entity in that regard? From this video it seems that they are part of the transaction: [this video] If not how do we preserve consistency in large scale applications?
Cites ehfeng · 2014-09 · Stack Overflow · on “Accessing Google App Engine's Search API from PHP”
The team promised that a REST API would be made available at Google I/O 2011. I haven't been able to find any follow ups since. [this video]
Cites quarks · 2014-10 · Stack Overflow · on “Full Text Search with Google App Engine”
I saw this video [this video] about Full Text Search in GAE, however I cannot find a way to see sample codes that will show Full Text Search using Datastore Entities as described in the video. Was the feature of Full Text Search for Datastore Entities actually did exist?
Cites Devraj · 2014-11 · Stack Overflow · on “DataStore Full Text Search documentation?”
This Google IO video [this video] from 2011 introducing the Full Text Search API (at 31:13), refers to DataStore Integration by setting a few properties in attributes. However I can't seem to find any related documentation to show how to go about using this feature. Does anyone know if anything's changed since the release of the API and if works in another way now? Any pointers will be greatly appreciated.
Cites srini · 2015-09 · Stack Overflow · on “GAE Full Text Search API on datastore entities using Golang”
I heard that we have app engine Search API support for Golang [LINK] . but it is not clear if we have can use this search API on GAE datastore entities (the Google IO 2011 video [this video] says it is possible, but not sure if that is really supported using Golang). Any thoughts about this? and any good documentation with examples? really appreciate your help.
Critical Janusz Skonieczny · 2012-05 · Stack Overflow · on “How to store lat-lon geolocation point in a document for GAE search?”
I think so myself, but I wasn't sure. The Google IO talk is somewhat misleading there is mention of GeoPoint [this video] but there is no such field. I did not know it was not released yet or API implementation have changed.