DataStore Full Text Search documentation?

[Devraj Mukherjee]

Hi all,

This Google IO 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.

Thanks.

Dev

[Vinny P]

On Sun, Dec 14, 2014 at 10:42 PM, Devraj Mukherjee <dev...@gmail.com> wrote:

This Google IO 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?

If you're talking about the searchType annotation showed in the video, it doesn't seem to have made it into production App Engine. The video you linked to was recorded in 2011, and the Search API went into public beta in 2012 - the video is describing an earlier version of search. 

The best way to emulate the datastore-search-api integration functionality is to define a post-put hook ( https://cloud.google.com/appengine/docs/python/ndb/entities#hooks ) - after storing an entity, you can have the hook insert a document into the Search API.

 

 

-----------------

-Vinny P

Technology & Media Consultant

Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

[Kaan Soral]

It's probably a much better idea to handle it in a pre-put hook and not always update the search document and mark it as updated when you do

Search seems to be very limited in terms of quotas (seems very limited, in reality it might be the opposite, I don't even see an index cap from the quota UI, yet it should be 1GB's or something)

There was also a hidden schema system a while ago, so watch out for that one, I guess it's improved now, but you could bust the schema and break the search feature for a single index, some while ago (so make sure you don't use many properties for the search document)

-----

I've been using and loving the search feature for a while now, without any issues

I have nearly a million entities indexed, the lack of quota/size information is a bit concerning :)