http://static.googleusercontent.com/external_content/untrust...
I believe this is available in both the Python and Java dev environments.
Additionally, http://code.google.com/appengine/docs/python/prospectivesear... might be of interest.
This is the reason the datastore forbids these operations - because they're extremely difficult to efficiently implement and still scale indefinitely (without making other, potentially very large sacrifices).
Hence why the datastore simply disallows this - yes, it's _possible_ to make joins work on larger datasets. But it's not possible to make _arbitrary_ joins work well on larger datasets.
InnoDB and MyISAM are not good at full text search even on local disk, no reason to make that worse.
Somewhat kinda germane post from Percona: http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-wi...
Since they forbid these operations on the datastore, I'm guessing this will either not scale as well or be significantly more expensive. Since the sign up sheet implies you can combine technologies, I suppose you can use a "hybrid" approach and keep denormalized data in the datastore.