Full-text search api [35875095]

Fixed

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Apr 15, 2008 09:39PM

The API currently offers a fairly limited functionality for text-search, based on the discussion on the
list:

http://groups.google.com/group/google-
appengine/browse_thread/thread/ba4a4a4ccefb96c5/0e3f0ab63c4c8afd?
lnk=gst&q=text+search#0e3f0ab63c4c8afd

I believe full-text search is fairly important feature for a lot of web applications. For god sake,
you're Google, how can you not? :-)

Comments

da...@gmail.com <da...@gmail.com> #2Apr 24, 2008 11:24PM

Project: r8
Branch: main
Author: Søren Gjesse <sgjesse@google.com>
Link: https://r8-review.googlesource.com/102486

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA

Expand for full commit details

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA 
 
From 1.000.000.000 to 3.600.000. 
 
The value was changed between the Baklava SDK revision 3 and revision 5. 
 
Bug: b/401489623 
Change-Id: I117585a1963c78f63be4e78663e5b8ce7dbc087b

Files:

M src/main/java/com/android/tools/r8/ir/desugar/BackportedMethodRewriter.java
M src/test/java/com/android/tools/r8/desugar/backports/AndroidOsBuildVersionCodesFullBackportTest.java

Hash: 28820ead67591243a497d93f06b4939f1bb6f898
Date: Fri Mar 07 14:06:11 2025

ku...@gmail.com <ku...@gmail.com> #3Jun 15, 2008 10:50AM

Project: r8
Branch: 8.10
Author: Søren Gjesse <sgjesse@google.com>
Link: https://r8-review.googlesource.com/102544

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA

Expand for full commit details

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA 
 
From 1.000.000.000 to 3.600.000. 
 
The value was changed between the Baklava SDK revision 3 and revision 5. 
 
Bug: b/401489623 
Change-Id: I117585a1963c78f63be4e78663e5b8ce7dbc087b

Files:

M src/main/java/com/android/tools/r8/ir/desugar/BackportedMethodRewriter.java
M src/test/java/com/android/tools/r8/desugar/backports/AndroidOsBuildVersionCodesFullBackportTest.java

Hash: 91276bda394605b8d449c573abe7eefa4a48bc88
Date: Fri Mar 07 15:59:40 2025

mh...@gmail.com <mh...@gmail.com> #4Jun 29, 2008 06:03PM

Project: r8
Branch: 8.10
Author: Søren Gjesse <sgjesse@google.com>
Link: https://r8-review.googlesource.com/102545

Version 8.10.14

Expand for full commit details

Version 8.10.14 
 
Bug: b/401489623 
Change-Id: I20612ce7bf580824cd2961e3db49a2e73430ba2b

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: c41c827ea5982bfb481b4d922b76e1a72db9a9d3
Date: Fri Mar 07 15:59:51 2025

ma...@gmail.com <ma...@gmail.com> #5Jun 30, 2008 06:11PM

Project: r8
Branch: 8.9
Author: Søren Gjesse <sgjesse@google.com>
Link: https://r8-review.googlesource.com/102413

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA

Expand for full commit details

Change the backported value of android.os.Build.VERSION_CODES_FULL.BAKLAVA 
 
From 1.000.000.000 to 3.600.000. 
 
The value was changed between the Baklava SDK revision 3 and revision 5. 
 
Bug: b/401489623 
Change-Id: I117585a1963c78f63be4e78663e5b8ce7dbc087b

Files:

M src/main/java/com/android/tools/r8/ir/desugar/BackportedMethodRewriter.java
M src/test/java/com/android/tools/r8/desugar/backports/AndroidOsBuildVersionCodesFullBackportTest.java

Hash: 42cef567f161d34a64e5565485d8f2a5802811eb
Date: Mon Mar 10 12:17:06 2025

ma...@gmail.com <ma...@gmail.com> #6Jul 1, 2008 11:18AM

Project: r8
Branch: 8.9
Author: Søren Gjesse <sgjesse@google.com>
Link: https://r8-review.googlesource.com/102414

Version 8.9.31

Expand for full commit details

Version 8.9.31 
 
Bug: b/401489623 
Change-Id: I035de3b90302456c31226b75be916dcb0cfbf681

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: d480e951bd7bdda26d0f9eac1725403c271b9fb7
Date: Mon Mar 10 12:17:18 2025

wk...@gmail.com <wk...@gmail.com> #7Jul 1, 2008 03:25PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Meerkat Feature Drop | 2024.3.2 Beta 1
Android Gradle Plugin 8.10.0-beta01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

de...@gmail.com <de...@gmail.com> #8Jul 1, 2008 04:16PM

The fixes for this issue are now also available in:

Android Studio Meerkat | 2024.3.1 Patch 1
Android Gradle Plugin 8.9.1

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

ro...@gmail.com <ro...@gmail.com> #9Jul 5, 2008 09:13AM

Ddza

mh...@gmail.com <mh...@gmail.com> #10Jul 5, 2008 06:34PM

https://issuetracker.google.com/401489623#attachment64415291

co...@gmail.com <co...@gmail.com> #11Jul 9, 2008 02:21PM

Me too

de...@gmail.com <de...@gmail.com> #12Aug 25, 2008 06:01PM

I need it also

ro...@gmail.com <ro...@gmail.com> #13Sep 6, 2008 06:55AM

I want this YESTERDAY!

va...@gmail.com <va...@gmail.com> #14Sep 19, 2008 04:00PM

Show stopper :-(

am...@gmail.com <am...@gmail.com> Sep 25, 2008 10:26PM

Assigned to am...@gmail.com.

tr...@gmail.com <tr...@gmail.com> #15Sep 26, 2008 03:01PM

Now that this issue has been acknowledged - it is equally important to note that full search in turn would need a
bigger limit of indexed values. Currently, it is impossible to make more than a few hundred words pr
row/article/post searchable as searchable indexed keywords are included in the limit.

aj...@googlemail.com <aj...@googlemail.com> #16Sep 26, 2008 06:23PM

We are all searching in the dark for both our text and when we can expect a
resolution to this major weakness in GAE. Road map please. Thanks.

ti...@gmail.com <ti...@gmail.com> #17Oct 1, 2008 08:51AM

I'm join to thread.

go...@gmail.com <go...@gmail.com> #18Oct 8, 2008 08:01AM

show stopper

me...@gmail.com <me...@gmail.com> #19Oct 29, 2008 07:02PM

+1000

ed...@gmail.com <ed...@gmail.com> #20Nov 20, 2008 10:39PM

hello, maybe it can help, I changed the code to a custom one, it work's nice to me,
maybe for you also, so:

class Cancion(mysearch.SearchableModel):
nombre_con_espacios_t = db.StringProperty()

the class must have the "nombre_con_espacios_t" attribute, because this attribute
will be the only attribute to be taken in acount to search.

it works as follow:

Creation:

cancion = Cancion(nombre_con_espacios_t="colombia es linda")
cancion.put()

Modification:

cancion.put(update_searchable=True)

Note, the FULL_TEXT_MIN_LENGTH_IN helps me to break more the regex :P

__init__.py

11 KB

View

Download

ed...@gmail.com <ed...@gmail.com> #21Nov 26, 2008 05:20PM

If some one find problems with it, would be great to know about those problems.

bo...@gmail.com <bo...@gmail.com> #22Dec 19, 2008 07:00AM

show stopper

ja...@gmail.com <ja...@gmail.com> #23Dec 19, 2008 07:07AM

definitely a show stopper, i've wrote a blog about search.SearchableModel and why it doesn't work, check it out if
you are looking for more info

http://zhuocorporation.spaces.live.com/blog/cns!D76A58A7350B0D0B!1824.entry

se...@gmail.com <se...@gmail.com> #24Jan 25, 2009 11:49PM

it is a must !!!!

se...@gmail.com <se...@gmail.com> #25Jan 27, 2009 12:47AM

It would be really nice to know if this feature has not only been acknowledged but if
it:s also somewhere on the roadmap.
It's not on the one published at

http://code.google.com/appengine/docs/roadmap.html
for the October 2008 - March 2008 period

I would really like to use App Engine seriously but like many people the lack of
full-text search could be a show stopper.
I can't see any good work around that would not require a huge amount of work.

I really hope full-text search will get a higher priority soon.

pa...@gmail.com <pa...@gmail.com> #26Jan 27, 2009 07:04AM

http://code.google.com/p/googleappengine/issues/detail?id=208&q=google%20api%20google%20app%20engine&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component

may be we should star the above issue. and once the google apis integrated directly
with app engine , we can just use google base for search. nice and dandy.

hu...@gmail.com <hu...@gmail.com> #27Feb 23, 2009 12:54AM

What an irony.

Google - the mother of all search engines, developed a cloud which doesn't offer a
text search in its API.

;-))))

It should have been the first function in the api. Isn't it all about search at
Google???

ch...@gmail.com <ch...@gmail.com> #28Feb 23, 2009 01:04AM

If anyone wants some rudimentary indexing and searching code shoot me a message. It basically stems and
filters stop words, then put the resulting list into a table that maps word to to the indexed objects. It sounds like
it could be slow but in practice it's been working fine. Currently the search is multi-word AND but extending it
to support phrases wouldn't be a big deal.

ri...@gmail.com <ri...@gmail.com> #29Feb 25, 2009 01:32PM

What about Google CSE? It's not something you can play on the server side,
but if your site is public and google likes it - quota free full text search :)

ja...@gmail.com <ja...@gmail.com> #30Feb 25, 2009 03:27PM

CSE is great for public sites but I still need unicode text search inside the
datastore to get the SQL functionality I am used to with commands like "LIKE
'xxx%yyy'". I hope we will have a solution for this issue soon... GAE is great!

bj...@gmail.com <bj...@gmail.com> #31Feb 28, 2009 12:31AM

It would be great to have full text search----PLEASE?!!!

cr...@hotmail.com <cr...@hotmail.com> #32Mar 1, 2009 05:17PM

jhjhjhhjhjh

ro...@gmail.com <ro...@gmail.com> #33Mar 4, 2009 11:47AM

Please add a search feature! I am a teacher using wordle in my classroom and it
would be soooo helpful!

se...@gmail.com <se...@gmail.com> #34Mar 4, 2009 03:17PM

this is a must

ta...@gmail.com <ta...@gmail.com> #35Mar 4, 2009 06:04PM

i believe that this would a great thing to have.

ya...@gmail.com <ya...@gmail.com> #36Mar 9, 2009 01:53PM

Highly required feature (especially when the service provider is Google)...

pa...@gmail.com <pa...@gmail.com> #37Mar 9, 2009 04:13PM

Just to like to add my name to the list of people hoping text search comes soon for
Wordle users.

sh...@gmail.com <sh...@gmail.com> #38Mar 9, 2009 04:18PM

searching text would be great!

go...@gmail.com <go...@gmail.com> #39Mar 10, 2009 04:53PM

how do i search for a wordle

tr...@gmail.com <tr...@gmail.com> #40Mar 10, 2009 05:01PM

It would be really great if you guys would stop writing a comment saying "Me too!", "This issue is crucial!" etc.
Can you please just follow normal procedure and star the item, so everybody at Google knows that this is an
issue many people care about (by counting stars), and I can stop getting your useless (no offense) comments in
my inbox? Thx.

go...@gmail.com <go...@gmail.com> #41Mar 10, 2009 05:04PM

please just help me i need to search something on wordle just go to this site then
try to search for a wordle

http://www.wordle.net/
i cant figure out how just go to the site figure out how to search for a wordle then
tell me please

go...@gmail.com <go...@gmail.com> #42Mar 10, 2009 05:05PM

i voted

go...@gmail.com <go...@gmail.com> #43Mar 10, 2009 05:09PM

by hiting the star so please help me search

gr...@gmail.com <gr...@gmail.com> #44Mar 12, 2009 03:41PM

Please address this issue!

oa...@gmail.com <oa...@gmail.com> #45Mar 13, 2009 12:23AM

Search is a must-have feature...

he...@gmail.com <he...@gmail.com> #46Mar 15, 2009 03:06AM

Yes, give me search on Wordle...otherwise I can never find my genial word-picture again!

pg...@gmail.com <pg...@gmail.com> #47Mar 16, 2009 02:51AM

As an educator it is vital that I be able to go in and find the word clouds my kids
have produced in order to trully validate their work. Please work on this.

cp...@163.com <cp...@163.com> #48Mar 17, 2009 01:05AM

Give me chinese fulltext search!

la...@gmail.com <la...@gmail.com> #49Mar 17, 2009 09:07PM

Really, really need to be able to search ....

[Deleted User] <[Deleted User]> #50Apr 2, 2009 02:43AM

Give me RLIKE !! regex support !!

ti...@gmail.com <ti...@gmail.com> #51Apr 6, 2009 10:24AM

cant we make a work around for it our self?

ko...@gmail.com <ko...@gmail.com> #52Apr 8, 2009 11:47AM

In usual web application it's possible to use Lucene or similar solution but
AppEngine doesn't proivde access to FS so we have no workaround here. IMO, it's must
have in order to be useful.

to...@gmail.com <to...@gmail.com> #53Apr 9, 2009 03:28AM

I vote that this is really a key restricting issue to better adoption of GAE.. Help
us please!!

ed...@gmail.com <ed...@gmail.com> #54Apr 10, 2009 12:32AM

Please, fulltext search now !

ce...@gmail.com <ce...@gmail.com> #55Apr 15, 2009 12:49PM

Another vote :)

ja...@gmail.com <ja...@gmail.com> #56Apr 16, 2009 09:51PM

like syntax please!

dr...@gmail.com <dr...@gmail.com> #57Apr 16, 2009 10:06PM

I have already starred this but would just like to say that this probably is the top
feature needed really. Now that Java has been added which adds numerous languages, I
think that searching is important because it is the next major performance hold up on
GAE and in most applications. Hoping this is in there soon! Keyword search is
actually one of the biggest walls on most projects. People might start using GAE just
to aggregate searching without a Google appliance.

Search is Google's killer feature, it could also be in the "cloud".

ar...@gmail.com <ar...@gmail.com> #58Apr 17, 2009 07:55PM

If you're using GAE/J, you might be interested in Compass, which sits on top of Lucene. It seems Compass works
in GAE/J as described here:

http://www.kimchy.org/searchable-google-appengine-with-compass/

ki...@gmail.com <ki...@gmail.com> #59Apr 20, 2009 11:52AM

ghs.google.com has been blocked in some countries, which means that your
users/clients in these countries are not able to access your GAE services with your
own domain name.

See

http://code.google.com/p/googleappengine/issues/detail?id=1269 for more details.

im...@gmail.com <im...@gmail.com> #60Apr 21, 2009 02:17AM

This is quite interesting actually.

http://www.dzone.com/links/searchable_google_appengine_with_compass.html

ar...@gmail.com <ar...@gmail.com> #61Apr 21, 2009 03:10AM

#63, yep, that's what I linked to in #61 :P

im...@gmail.com <im...@gmail.com> #62Apr 21, 2009 04:00AM

Sorry Arthur, I missed it then :)

ar...@gmail.com <ar...@gmail.com> #63Apr 21, 2009 04:05AM

With so many comments, I would have missed it too ;)

ex...@gmail.com <ex...@gmail.com> #64Apr 30, 2009 02:56PM

+1, it would be great if Search API could be provided. I have been using the
Searchable Model for quite sometime, and it fits to my basic needs, but i know a
search engine that has made the expectations of people really high, as soon as they
see a search box :-)

oz...@gmail.com <oz...@gmail.com> #65Apr 30, 2009 06:20PM

when I went through the features of GAE, I neglected to inspect the one feature that
couldnt be missing: "eh, it is google, so why waste time to check that full-text
search is there?". now it is time to place the search box on the page and I'm lost.

ps. the priority of this issue is just "medium" and roadmap doesnt include a solution
yet. beautiful..

zb...@gmail.com <zb...@gmail.com> #66Apr 30, 2009 07:38PM

Please stop adding pointless comments with no new information. Spamming over a 1100
people that starred the issue with "me too" or "+1" comments doesn't get it done any
faster. I bet google already knows we want it. Thanks.

wk...@gmail.com <wk...@gmail.com> #67May 2, 2009 09:53AM

Hi everyone,
we're the developers behind app-engine-patch
(

http://code.google.com/p/app-engine-patch/). We'd like to sell our "search" package
which provides a more powerful feature set than SearchableModel and should help make
the wait for Google's full-text search API less painful. The features are described
in this post:

http://tinyurl.com/dxen3z

If you're potentially interested in buying our search package (for a
one-time fee) please take part in this short survey, primarily to help
us find a fair price:

http://www.surveymonkey.com/s.aspx?sm=CzIohuPfdcTL8z484vcX4Q_3d_3d

While there is not yet a demo site we hope that you can at least give
an approximate estimate. Thanks a lot!

Best regards,
Waldemar Kornewald

ga...@gmail.com <ga...@gmail.com> #68May 8, 2009 11:28PM

I have created a full text search api by porting

http://whoosh.ca/ so it is avaliable
on AppEngine. (it stores the index in the datastore)

You can download it from

http://github.com/tallstreet/Whoosh-AppEngine/tree/master

It includes all of Whooshes features including:

# Pythonic API.
# Fielded indexing and search.
# Fast indexing and retrieval
# Pluggable scoring algorithm (including BM25F), text analysis, storage, posting
format, etc.
# Powerful query language parsed by pyparsing.
# Pure Python spell-checker

wk...@gmail.com <wk...@gmail.com> #69May 9, 2009 09:31AM

Nice! How many entities can be handled efficiently with your whoosh port? Do you have
any real-world data on how well it handles concurrent writes?

sa...@gmail.com <sa...@gmail.com> #70May 9, 2009 08:33PM

Similar question as wkornewald -- how will something like this scale? You indicate
that the index is stored in the Google Datastore. Does this mean that it should
scale as well as the GAE datastore does (~1 - 10 writes per second, etc).

ta...@gmail.com <ta...@gmail.com> #71May 9, 2009 11:26PM

The only real world app using this at present is

http://appjects.appspot.com/ (all
categories and searches are powered by it).

Adding a document requires 4 writes and 4 deletes to the datastore.

Its not threadsafe, I recommend you add entities on one thread and index them in a
single thread on a cron.

I've put memcache caching on the index so searching should be very quick.

The other limitation will be the size of the index, it uses the same index file
format that whoosh uses but just stores the files in the datastore, therefore the
whole index is stored in a 4 datastore entities, I believe there is a 10 Mb limit on
each one?

wk...@gmail.com <wk...@gmail.com> #72May 10, 2009 10:53AM

It's actually a 1MB limit. Is there no possibility to distribute the index across
more than 4 datastore entries?

Also, I quickly skimmed through the source and I haven't seen a command for splitting
the indexing task into many small tasks, so you don't hit the request limits. Is
there anything like that?

md...@gmail.com <md...@gmail.com> #73Jun 10, 2009 05:52PM

Hi Waldemar,

In one of your posts you indirectly suggest that Google might someday be releasing a
full-text search API.

Based on the social evidence to date, though, I wouldn't be so sure about that.

Do you really believe that Google has intentions of extending GAE with full-text
search and if so, why?

wk...@gmail.com <wk...@gmail.com> #74Jun 10, 2009 06:31PM

Hi! Well, Google developers indicated in presentations that they have it on their
roadmap, but it's very complicated and thus won't be added too soon (don't expect it to
be released this year). I don't see why Google wouldn't want to add that feature.
Without full-text search App Engine is very limited. I'm sure that sooner or later
we'll get it. :)

md...@gmail.com <md...@gmail.com> #75Jun 11, 2009 01:58AM

Waldemar

I sure hope that's the case but something is telling me that this full-text search
issue might be more about the law of unintended consequences than a good
old-fashioned technical challenge.

Could full-text search on AppEngine somehow threaten Google's search and advertising
franchise? If so, that would explain a lot.

Also, I was a little disheartened to hear you suggest full-text search might not be
available until 2010 at the earliest.

Seems very odd to me, especially given the Bay Area operates at warp-speed.

le...@gmail.com <le...@gmail.com> #76Jun 11, 2009 04:22AM

[Comment deleted]

le...@gmail.com <le...@gmail.com> #77Jun 11, 2009 04:27AM

This isn't about threatening Google's business model. App Engine itself generates revenue.

Unfortunately, full-text search isn't trivial. Further, Google generally does not announce features before they are
available. When pressed, Googlers tend to indicate how important they think a feature is, and then announce
that they "have nothing to announce."

Brett Slatkin, a developer on the App Engine team, indicated that they are well aware of how many developers
want full-text search. Watch

http://tinyurl.com/lug7j5 to see him address the issue. As he mentioned, there is
support for rudimentary full-text search via the google.appengine.ext.search module. See

http://tinyurl.com/3ndnge for some documentation.

ap...@gtempaccount.com <ap...@gtempaccount.com> #78Jun 24, 2009 11:10AM

Hi,
we'd like to announce the immediate availablility of our full-text search package
(based on the same principle as SearchableModel, but much more flexible and
feature-rich).
It's called gae-search:

http://gae-full-text-search.appspot.com/

See it in action by searching our documentation (which is indexed with gae-search).
We also have a few demos.

Note that gae-search requires app-engine-patch (Django).

Features:
* index only specific properties (instead of all string/text properties like in
SearchableModel)
* Porter stemmers (increase search quality)
* sort your results (at least a little bit) via chain-sorting
* make "DISTINCT" queries using a so-called "values index"
* auto-completion via a jQuery plugin
* key-based pagination (fully unit-tested implementation of Ryan Barrett's algorithm)
* easy to use views and templates (add search support in just a few lines)

Since it took a lot of effort to implement all features and make them easy to use we
can't give this away for free, though. We initially implemented it for our own
projects, but after so many people complained about the lack of full-text search we
though we could provide it to others - for a little compensation.

Bye,
Waldemar Kornewald & Thomas Wanschik (the creators of app-engine-patch)

to...@gmail.com <to...@gmail.com> #79Jun 26, 2009 05:47AM

See the following article for a simple search

http://www.devx.com/Java/Article/42216

sh...@gmail.com <sh...@gmail.com> #80Jun 27, 2009 12:22AM

Is there such a patch for java platform?

wk...@gmail.com <wk...@gmail.com> #81Jun 28, 2009 12:51PM

app-engine-patch is only available for Python. I don't know if there is some comparable
App Engine project on the Java side. Currently, we have no plans to port gae-search to
Java (well, unless there is really high demand which would justify all the work
involved).

sh...@gmail.com <sh...@gmail.com> #82Jun 29, 2009 11:43PM

IC,
so I need to switch to GAE for Python.
Where is the demo for using SearchableModel to do full-text search available?

bi...@gmail.com <bi...@gmail.com> #83Jun 30, 2009 05:26AM

I just released a simple full text search module for GAE python under a MIT license. I
believe it is better than SearchableModel. For more details, see:

http://bit.ly/11yLv5

sh...@gmail.com <sh...@gmail.com> #84Jul 2, 2009 09:53PM

That's cool,

but is it possible to search within a specified document?

sh...@gmail.com <sh...@gmail.com> #85Jul 2, 2009 10:01PM

I think I need to talk about it more specificly.

By default we search a keyword against many documents.

But now I've restored 1M keywords in datastore and a specified document.

I want to find out which of 1M keywords match the specified document.

Is there an efficient solution?

bd...@gmail.com <bd...@gmail.com> #86Jul 2, 2009 10:46PM

@shore.cloud:

What you describe is not full-text search. You should ask for advice on the google
group; this bug is subscribed to by over a thousand people, and should only be used
for on-topic discussions.

sh...@gmail.com <sh...@gmail.com> #87Jul 3, 2009 10:01PM

@bdonlan,
sorry for off-topic.

One more thing I want to know about full-text search is:

Is it possible to restrict the range of documents?

Say,sometimes I want to search about 'news',sometimes about 'job'?

It seems by default all entities are indexed together?

ap...@gtempaccount.com <ap...@gtempaccount.com> #88Jul 10, 2009 09:11AM

Hi,
we've released a new gae-search version (full-text search for App Engine + Django).
Now, there's a "Free" version which can be used in non-commercial projects. Get it here:

http://gae-full-text-search.appspot.com/

We've also implemented the relations index technique (index is moved into a separate
child entity), but you can optionally turn it off. It's important to note that you
can integrate your model's properties into the generated index such that you can run
a full-text search and limit the results with additional filter rules (e.g., search
only in published blog posts).

The relations and values indexes are now generated via background tasks, so put()s
are much faster.

Finally, you can combine geomodel with our easy to use views in order to do a
full-text proximity search, for example. Just use the new query_converter parameter
to pass the full-text query to geomodel.

Bye,
Waldemar Kornewald & Thomas Wanschik

sw...@gmail.com <sw...@gmail.com> #89Jul 13, 2009 05:30AM

:-)

sh...@gmail.com <sh...@gmail.com> #90Jul 23, 2009 12:15PM

full text support for all languagues is needed!

lu...@gmail.com <lu...@gmail.com> #91Aug 3, 2009 01:33PM

I think this would be a simpler to implement solution that would put the workload on
us, developers, and would give us a powerful tool to do much more than just full-text
search.

http://code.google.com/p/googleappengine/issues/detail?id=1935

be...@gmail.com <be...@gmail.com> #92Sep 23, 2009 06:09AM

a warning to anybody planning to use listproperty based fulltext implementations. list based fulltext search is
based on the fact that AND joins are done if one filters on the same attribute more than one time like:

q = Doc.all().filter('term', 'cat').filter('term', 'dog)

this does work in first place without the need of an exploding index which (in practice cannot be built on
appgine if you have long lists of words or many docs). indexe entries would look like this.

- kind: Doc
properties:
- name: term
- name: term

there must be some internal limit on appengine that prevents joins with many intermediate results. so this
pattern is not applicable for real world applications.

up till now any fulltext implementation i have seen so far for appengine is based on this pattern, so don't use
it.

ma...@gmail.com <ma...@gmail.com> #93Oct 2, 2009 09:20PM

Accepted by am...@gmail.com.

I'm marking this issue as "Started" but I want to set expectations appropriately:
This is a major undertaking and this will not happen soon, even by the most generous
definition of soon.

[Deleted User] <[Deleted User]> #94Oct 2, 2009 09:29PM

This is a very good news :)

ne...@gmail.com <ne...@gmail.com> #95Oct 2, 2009 10:22PM

Wow! I'm very happy to hear that. Please let us know when you need testing help etc.

jd...@gmail.com <jd...@gmail.com> #96Oct 3, 2009 05:28AM

I am curious if the approach is to supply an out of the box take-it-or-leave-it search or to provide the low level
tools required to implement something like a distributed Lucene index. Will it be based on Map Reduce? Good
new in any case!

[Deleted User] <[Deleted User]> #97Oct 3, 2009 08:20AM

Wow, I never saw "Started" before :) Anyway, please give us a "rouge" Roadmap, "will
not happen soon" ... its 6 months, 1 year or 2+ years? There are many developers who
need this feature urgent, I've stopped most of my appeninge activity because I've
fight with too many limitations. But I'm very excited about the recent changes, just
miss a more detailed roadmap.

lu...@gmail.com <lu...@gmail.com> #98Oct 3, 2009 10:55AM

So happy see the status has changed.. you guys rock.

kr...@gmail.com <kr...@gmail.com> #99Oct 21, 2009 03:26PM

www.google.com

ba...@gmail.com <ba...@gmail.com> #100Nov 24, 2009 03:45PM

n-gram for japanese please.

sf...@gmail.com <sf...@gmail.com> #101Dec 2, 2009 11:12AM

please, in a first step, increasing the limit of 5000 indexes could allow to wait
until the arrival of a real full text search solution and unlock many projects.

pr...@gmail.com <pr...@gmail.com> #102Dec 19, 2009 09:00AM

Happy to see the started status. At least the wheels are rolling. We will get to
destination..

cr...@gmail.com <cr...@gmail.com> #103Jan 11, 2010 12:37PM

I also need it. In English, as well as in Chinese, etc...

ca...@gmail.com <ca...@gmail.com> #104Jan 15, 2010 02:00AM

Will it be like the SearchableModel where you can filter() and order().

Thanks,

i....@gmail.com <i....@gmail.com> #105Jan 15, 2010 03:53AM

This is an important feature for web app especially for serious app that has a lot of
data. Will it support other languages other than English?

my...@gmail.com <my...@gmail.com> #106Jan 16, 2010 04:49AM

n-gram for Traditional Chinese too, Pls.

vv...@gmail.com <vv...@gmail.com> #107Jan 16, 2010 12:02PM

Can you guys all give the Soundex function a look so that it can be used during
Full-text search based on similar sounding words...

ja...@gmail.com <ja...@gmail.com> #108Mar 3, 2010 11:34AM

Is there an eta or a road map for this?

nj...@gmail.com <nj...@gmail.com> #109Mar 15, 2010 02:33AM

I starred this issue based on the following design issue

My case:
I am building a website that has several searchable fields from
various entities (example Artist names from artist entity , Album
names from album entity). To have an efficient search capability I
have defined another Entity - SearchType which carries the Searchable
string and the Foreign key to the Entity. Instead of querying all the
Entities one my one - I query SearchType.

My preliminary tests indicate that the query performance on
SearchType is not great (the names are indexed) . I need google
suggest like quick results in a drop down. What is the best way to
design this.

I have considered Memcache , but I dont think I can run queries on
Memcache . i.e I am running a startsWith() query on JDO today.

Any best practices .

dd...@gmail.com <dd...@gmail.com> #110Mar 18, 2010 10:52PM

one of important features for my apps..Please

da...@gtempaccount.com <da...@gtempaccount.com> #111Mar 19, 2010 03:14PM

Very important feature! After use it for a while I cant believe it just cant search.... what
a shame...

mo...@gmail.com <mo...@gmail.com> #112Mar 29, 2010 02:07AM

Need it

ev...@gmail.com <ev...@gmail.com> #113Mar 29, 2010 09:19AM

Thanks for starting!

ya...@gmail.com <ya...@gmail.com> #114Mar 31, 2010 11:33AM

We are too considering to port our applications to GAE but lack of relational query
support and full text search query are biggest hindarance.

ph...@gmail.com <ph...@gmail.com> #115Apr 7, 2010 10:01PM

after spending several months building our apps on GAE, we are now thinking about taking out and moving to
Amazon. We tried using compas and it fails after we over only a few thousand entries. Unless we hear back soon,
we most likely will just abandon all and never look back at GAE again.

au...@gmail.com <au...@gmail.com> #116Apr 10, 2010 10:04PM

i m sure you are giving the right priority, many need this feature. you guys rock !!

fi...@gmail.com <fi...@gmail.com> #117May 21, 2010 12:28AM

Is there any change in plans for full text search API with the new GAE for Business announcement? I'm pretty sure
this is far more demanded by business then SQL.

tr...@gtempaccount.com <tr...@gtempaccount.com> #118May 24, 2010 11:57PM

How can anyone seriously build a web app without full text search?

I guess the work around is to install Solr on some EC2 instance and have it suck data from DataStore...

al...@gmail.com <al...@gmail.com> #119Jun 2, 2010 02:22AM

I have started a project in App Engine I have learned Python for that and when I go to
program a search, I find that it's very difficult... that it's not implemented.

I really want use App Engine... it's a wonderfull platform, but without fulltext
search I can't.

Please implement the fulltext search and will give to much people a great reason for
smile...

bo...@gmail.com <bo...@gmail.com> #120Jun 20, 2010 10:43PM

Full-Text-Search is a real life very common need!!!

pa...@gmail.com <pa...@gmail.com> #121Jun 30, 2010 11:21PM

I don't get it. The rest of GAE is so brilliant, how is this still not working?

vi...@gmail.com <vi...@gmail.com> #122Jul 1, 2010 10:34AM

Having double thoughts about GAE. Can't be managing an external server for search and transferring data to and forth. And looking at the response to this issue, it seems google doesn't care either. Maybe they are thinking hard on how to monetize and automatically get deep integration into the search of all apps hosted. Whatever. Been waiting for long for this feature.

cr...@gmail.com <cr...@gmail.com> #123Jul 5, 2010 05:37PM

Full text search support please...

cr...@gmail.com <cr...@gmail.com> #124Jul 5, 2010 05:39PM

Any idea of the best workaround while waiting for a google release ?

ja...@gmx.de <ja...@gmx.de> #125Jul 10, 2010 11:46AM

I'm looking forward to it - but as with everything else in datastore world the FTS solotion should have a faily good performace for all common (basic) cases. Otherwise it seams to be nearly useless to me. Than I would end up in the workaround I already build myself.

ni...@gmail.com <ni...@gmail.com> #126Jul 13, 2010 09:55PM

Need FTS

az...@gmail.com <az...@gmail.com> #127Jul 21, 2010 01:07AM

Big need !
Guys, you'r the FTS nynjas of the web, come on ..

ma...@gmail.com <ma...@gmail.com> #128Jul 22, 2010 06:24PM

My sadness is infinite.

kl...@gmail.com <kl...@gmail.com> #129Aug 8, 2010 05:52PM

please

ma...@gmail.com <ma...@gmail.com> #130Aug 12, 2010 01:49PM

My sadness is also infinite :)

hs...@gmail.com <hs...@gmail.com> #131Aug 17, 2010 02:57PM

FYI, I've created this issue:

http://code.google.com/p/googleappengine/issues/detail?id=3592)
requesting support for Lucene/SOLR support (instead of a potentially proprietary implementation)

ma...@gmail.com <ma...@gmail.com> #132Aug 20, 2010 12:46PM

I think I'd rather have something GAE-specific rather than Solr/Lucene. Somehow, I can't imagine either one of those playing well with Google's infrastructure.

je...@gmail.com <je...@gmail.com> #133Aug 26, 2010 07:28PM

I for one have started a library that interfaces Lucene and GAE together, it's definitely alpha and it won't scale very big, but it does work if the data being indexed and searched is small enough to fix in the heap space provided by GAE. Once I get it stable using in memory indexes, I'm planning to work on a new Directory implementation that works directly with datastore and memcache instead of copying to/from datastore working in-memory then writing changes back to datastore.

Although it might be throw away code once Google's solution is ready, it's been a fun challenge to work on this, and I would welcome input from others.

http://code.google.com/p/lucene-for-gae/

a....@gmail.com <a....@gmail.com> #134Sep 7, 2010 09:01AM

Waiting impatiently for the feature. Full text search is a must when you have user generated content involved.

wm...@gmail.com <wm...@gmail.com> #135Sep 9, 2010 10:00PM

Full text search is definitely a must have.

nj...@gmail.com <nj...@gmail.com> #136Sep 11, 2010 04:46AM

Any idea when this will be done. Waiting ..... Waiting....

al...@gmail.com <al...@gmail.com> #137Sep 15, 2010 08:12AM

I can't deploy my idea on app engine without full text search support...

sv...@gmail.com <sv...@gmail.com> #138Oct 8, 2010 05:29AM

Extremenly critical feature.

co...@gmail.com <co...@gmail.com> #139Oct 9, 2010 05:14PM

please...
big need

ad...@gmail.com <ad...@gmail.com> #140Oct 14, 2010 02:16AM

FYI I worried about this for a long time, then "timed out" and now recommend Apache SOLR:
- very easy to install and configure
- very reliable i.e. near-zero maintenance
- inexpensive to host, e.g.

linode.com = $20/mon
- has more features than Google's v1 solution is likely to have
reply if you want me to writeup instructions and post a link here.

pr...@gmail.com <pr...@gmail.com> #141Oct 16, 2010 03:22PM

Please address this issue asap ... text based search is an essential feature for most of the apps.

de...@gmail.com <de...@gmail.com> #142Oct 27, 2010 06:02PM

...would be grand, thanks.

fb...@gmail.com <fb...@gmail.com> #143Nov 10, 2010 11:50PM

I would be very happy if you added case insensitive search and prefix search (startswith).

If you also added some regexp/glob-like search I'd be even happier.

Btw, if you need help on that, don't hesitate to ask. I like appengine and use it for some of my projects. I wouldn't mind helping out if that is what is needed.

ge...@gmail.com <ge...@gmail.com> #144Nov 29, 2010 05:57PM

oh yeah!

[Deleted User] <[Deleted User]> #145Dec 5, 2010 12:44AM

[Comment deleted]

go...@gmail.com <go...@gmail.com> #146Dec 20, 2010 06:28AM

@ adam.sah
We'd definitely appreciate a write up of instructions and a link. Please do. =)

no...@gmail.com <no...@gmail.com> #147Dec 29, 2010 02:17PM

If I were to host an external service such as SOLR, where would be the best location to have it hosted to have the lowest latency to GAE?

fh...@gmail.com <fh...@gmail.com> #148Jan 5, 2011 12:48PM

Necesitamos FTS

ec...@gmail.com <ec...@gmail.com> #149Jan 16, 2011 09:48AM

Of course it'll be great to have FTS which has `native` API for GAE.

dr...@gmail.com <dr...@gmail.com> #150Jan 23, 2011 11:43PM

Definitivamente necesitamos búsquedas de texto completo!!!

st...@gmail.com <st...@gmail.com> #152Jan 27, 2011 02:28AM

For a moment i thought this API was live. I hope it is about time...

ve...@gmail.com <ve...@gmail.com> #153Jan 27, 2011 02:33AM

Thanks for the update.
Is there an ETA when this would be resolved? If you can provide a rough estimate in terms of weeks/months, that would help us in planning for projects which need FTS.

Thanks
-Venu

ja...@gmail.com <ja...@gmail.com> #154Jan 27, 2011 10:08AM

ETA would be great! We start our project on GAE, and plan beta for June. Having to setup Solr on EC2 and logic to feed it and query it, puts unnecessary obstacles on the way that steals focus from application itself, which doesn't the fast prototype and beta plan. Also this technology solution seems obsolete by design from a longer perspective.

C'mon Google, we know you can do FTS :)

sb...@gmail.com <sb...@gmail.com> #155Feb 8, 2011 01:19AM

ETA pls

do...@gmail.com <do...@gmail.com> #156Feb 9, 2011 08:53PM

Please can we have a rough timescale on this critical issue?
Full text search is pretty fundamental to most apps.

ve...@gmail.com <ve...@gmail.com> #157Feb 12, 2011 04:02PM

I hope it will support UTF-8

ma...@gmail.com <ma...@gmail.com> #158Feb 21, 2011 08:14PM

please, please, please

al...@gmail.com <al...@gmail.com> #159Mar 3, 2011 05:43PM

Please!

yc...@gmail.com <yc...@gmail.com> #160Mar 6, 2011 02:27AM

please :(

ma...@gmail.com <ma...@gmail.com> #161Mar 15, 2011 11:44AM

please ! :)

ja...@gmail.com <ja...@gmail.com> #162Mar 22, 2011 06:05PM

Am I the only one who thinks that there might be purpose/plan in not giving developers such vital function as FTS?

We are waiting **3 years** now for Full Text Search in Google AppEngine. That alone sounds incredibly to me. Now add to it that we don't see any signs of progress whatsoever. (When was it last time anyone from Google even mentioned this function anywhere, like on Google I/O?)

Wild guess: could it be that Google wants us to rather use/implement their site-search?

me...@gmail.com <me...@gmail.com> #163Mar 25, 2011 03:41PM

Please GAE team give us rough timeline for the release of FTS. We are eagerly waiting for it.

me...@binaryblur.com <me...@binaryblur.com> #164Mar 30, 2011 10:55PM

I'd like to suggest HoundSleuth (

http://www.houndsleuth.com) for GAE full-text search. It has a full Python client implementation in github and can easily be ported to the Java SDK too. It's fast, secure, and scales to any data-set size. It also support relevance ranking, stemmers, sorting and grouping.

me...@gmail.com <me...@gmail.com> #165Apr 20, 2011 06:04PM

I have used whoosh for fulltext search in my site

http://www.lolzwow.com. Its working fine for me. For the time being for fulltext search in webapp whoosh is one of the good solutions.

do...@gmail.com <do...@gmail.com> #166May 4, 2011 03:47PM

It seems like the Google will be announcing the Full Text Search capabilities at the Google I/O. They have an entire session dedicated to the topic:

http://www.google.com/events/io/2011/sessions.html

do...@gmail.com <do...@gmail.com> #167May 12, 2011 07:35PM

Hi,
you asked for some feedback at IO 2011. Not sure this is the best forum, but anyhow - here goes!

The slides mentioned a numeric search field. If I have a 3500 character length document and want to create roughly 3500 numeric tokens for that document, can I then execute a search using OR operators and numeric inputs?

For example:

Document with ID 798 has the following 3500 numeric tokens:

745678465,92892348,2904983,.......,4538748,4579843,548975

I want to search by specifying something like 3200 inputs:

34837434 OR 75647856 OR 56475864 OR ............ OR 4579843

And for the scoring to be based on number of positive matches. Is this feasible within the full text search performance boundaries. It is possible with the Datastore and ListProperties, but proved very costly in API usage.

Also do you intend to provided faceting of search results? For example can, I specify 20 results per date within a specified date range?

Cheers,
Donovan

ga...@gmail.com <ga...@gmail.com> #168May 12, 2011 09:59PM

Hello,

You asked for feedback, not sure if this is the correct place.

I just watched the Google IO talk on full text search and I'm really impressed - just what I need. Thanks very much, please release the core API ASAP and worry about the REST interface etc. later!

From what I saw, the API seems great but there might to be an issue with apps using namespaces. The presentation implied that search results would be returned for a kind from all namespaces. I think that people will want a bulletproof way of ensuring that indexes are created, and search results returned on a per-namespace basis. If you have a multi-tenancy app then you need to be assured that someone else's data won't be returned.

I may have misunderstood and this is already available.

Once again, thanks very much. Once this is available it will make my app much better and allow me to remove all the awful kludge code that I've put in to try solve the problem of searching.

nu...@gmail.com <nu...@gmail.com> #169May 15, 2011 05:12AM

Just saw the Google I/O video on FTS. The presenter was like "we want you to give us feedback". This made me think the API has been released. But doesn't look like it right now. Anyone know when it is scheduled to be released?

pu...@gmail.com <pu...@gmail.com> #170May 21, 2011 03:01AM

Where is it? Please give us a timeline .. This is really important for us !!

ga...@lolay.com <ga...@lolay.com> #171May 26, 2011 06:28PM

It would be great if there is a way to participate in a beta as in our app we already built our own search, but it's crude and limited (i.e. task queues, tokenizer, index tables).

pu...@gmail.com <pu...@gmail.com> #172Jun 2, 2011 09:53PM

C'mon there could atleast be a beta ..

fa...@gmail.com <fa...@gmail.com> #173Jun 9, 2011 11:11AM

The io session looked like exactly what I've been waiting for. Now if only I could take it for a spin...

sa...@gmail.com <sa...@gmail.com> #174Jun 14, 2011 02:40PM

hurry up!

sn...@gmail.com <sn...@gmail.com> #175Jun 29, 2011 01:38PM

Any news on the release of this? We also need it for our project and are debating whether to create our own.

wl...@gmail.com <wl...@gmail.com> #176Jul 4, 2011 01:40PM

When's this coming, can't wait.

sa...@gmail.com <sa...@gmail.com> #177Jul 14, 2011 10:24PM

I have watched google IO session for "full text search". Any update when this will be released?

rv...@gmail.com <rv...@gmail.com> #178Jul 20, 2011 02:59AM

yeah, the google IO sessions mentioned beta invites for feedback. What happened to that? Also, the status showing as "Started" gives no indication on when this will be available.
Come on, don't do this google. If you don't release often then the chances of the whole project being killed are quite high.

pr...@google.com <pr...@google.com> #179Jul 20, 2011 01:23PM

Full Text Search in on the official App Engine team roadmap:

http://code.google.com/appengine/docs/roadmap.html

il...@gmail.com <il...@gmail.com> #180Jul 20, 2011 01:29PM

Keep up the good work!

kj...@gmail.com <kj...@gmail.com> #181Jul 20, 2011 04:34PM

it's a good new! thanks

lp...@gmail.com <lp...@gmail.com> #182Jul 24, 2011 07:08PM

Any estimate when this feature is going to be available?

pu...@gmail.com <pu...@gmail.com> #183Jul 25, 2011 01:58AM

Damn! This is really testing patience!

sa...@gmail.com <sa...@gmail.com> #184Jul 26, 2011 08:04PM

Man, I really want this feature. Don't want to have to figure out Lucene if I don't have to!

sa...@gmail.com <sa...@gmail.com> #185Aug 18, 2011 10:53AM

No news when that feature will be realized ?

pu...@gmail.com <pu...@gmail.com> #186Aug 19, 2011 06:23AM

2292 people starred this issue. When Google when? How about an update?

ca...@gmail.com <ca...@gmail.com> #187Aug 26, 2011 01:18PM

What about core api? Isn't about time to have it?

mm...@googlemail.com <mm...@googlemail.com> #188Aug 27, 2011 06:12PM

PPPPP HH HH PPPPP
PP PP HH HH PP PP
PPPPP HHHHHHHH PPPPP
PP HH HH PP
PP HH HH PP

It's necessary!
Please.

na...@gmail.com <na...@gmail.com> #189Aug 31, 2011 09:12AM

Long three years...And no FTS. Fail!

[Deleted User] <[Deleted User]> #190Sep 7, 2011 11:14AM

You can have a look at full text search with dev_appserver.py
Everything seems to work fine (at least as expected after viewing the IO recordings)

ri...@gmail.com <ri...@gmail.com> #191Oct 28, 2011 04:47PM

Bo/Ged,

Any chance of adding this functionality to the JAVA dev server for testing? I know you can't give timelines -- but testing the functionality on our local dev servers would allow us to architect systems that can be deployed once it is ready.

Thanks,
- Chris

[Deleted User] <[Deleted User]> #192Nov 27, 2011 03:35AM

@Chris ... you don't need to hurry .. I think a such api will be available in 2013 so there is enough time to architect other things before this . I'm waiting for the SSL support for 2 years and until now we got just two "trials" which actually were just two google spreadsheets that I had to complete and I got no response whether I got qualified to test it or not .

mj...@gmail.com <mj...@gmail.com> #193Dec 22, 2011 03:53AM

where can we find the guestbook code demonstrated at IO 2011?

mj...@gmail.com <mj...@gmail.com> #194Jan 2, 2012 10:26PM

got most of the IO example working but date fields aren't searchable using date:[TO 2012-01-023] syntax. is this supposed to work in latest dev_appserver?

ko...@gmail.com <ko...@gmail.com> #195Feb 5, 2012 05:29AM

I really need this. There are no alternative?

[Deleted User] <[Deleted User]> #196Feb 14, 2012 10:18PM

4 years and still now full search text.

ci...@google.com <ci...@google.com> #197Feb 14, 2012 10:25PM

Full text search is available to trusted testers. See:

http://googleappengine.blogspot.com/2011/10/app-engine-155-sdk-release.html

[Deleted User] <[Deleted User]> #198Feb 14, 2012 10:28PM

[Comment deleted]

[Deleted User] <[Deleted User]> #199Feb 14, 2012 11:32PM

[Comment deleted]

zl...@gmail.com <zl...@gmail.com> #200Feb 15, 2012 03:09AM

sorry guys, 4 year it's toooo late

dl...@gmail.com <dl...@gmail.com> #201Feb 15, 2012 01:26PM

The trusted tester program is all well and good, but I signed up two weeks ago and have not heard anything, not even a confirmation e-mai. A poster up above similarly describes signing up for the SSL trials and never hearing back. Sounds like a nebulous process.

Who is this Christina person? She sounds helpful, maybe we need to get in touch with her :)

sb...@gmail.com <sb...@gmail.com> #202Feb 15, 2012 05:08PM

likewise, i signed up several weeks ago, havent heard back from google. what should i do to be trusted? i feel somewhat upset to choose Saas. you are always at the mercy of developers. and you are locked either vendor specific code, or wait someone to wrap and adopt it to current enviroment.. response to issues are damn slow, and now you abstract the app engine groups, to stackoverflow.. i wish i go with known technologies like mongodb, nodejs, ec2..

[Deleted User] <[Deleted User]> #203Mar 8, 2012 02:20PM

this is a show stopper, i tried to switch between cloud-sql, and other platforms.
we need full text search. like %% etc. this is an absolute must for any normal web application. please do something about it.

az...@gmail.com <az...@gmail.com> #204Mar 8, 2012 07:44PM

This is absolutely pathetic, Who actually are the indented audience for GAE? You guys don't have FTS and working on minor used features?

nu...@gmail.com <nu...@gmail.com> #205Apr 14, 2012 10:04PM

beside the cruel irony not having FTS i am starting to wonder why it would take google so long to implement this? is it because the gae team is under resourced? i am frankly puzzled...btw amazon released cloudsearch.

ca...@gmail.com <ca...@gmail.com> #206May 8, 2012 02:12AM

GAE4PHP!!!

ie...@google.com <ie...@google.com> #207May 9, 2012 05:28PM

Marked as fixed.

Full text search is now available for you to try out. See this blog post for more information -

http://googleappengine.blogspot.com/2012/05/looking-for-search-find-it-on-google.html

Python Overview -

https://developers.google.com/appengine/docs/python/search/overview

Java Overview -

https://developers.google.com/appengine/docs/java/search/overview

ve...@gmail.com <ve...@gmail.com> #208May 26, 2012 07:01AM

[Comment deleted]

ve...@gmail.com <ve...@gmail.com> #209May 26, 2012 07:02AM

So Great

[Deleted User] <[Deleted User]> #210Sep 15, 2012 06:30AM

no faceted search ?

zi...@gmail.com <zi...@gmail.com> #211Oct 26, 2012 01:49AM

please help i want to create a wordle

ma...@gmail.com <ma...@gmail.com> #212Jul 30, 2022 10:34AM

Ever since Dr. John helped me, my partner is very stable, faithful and closer to me than before. I highly recommends Dr. John to anyone in need of help. Email: Drjohnsoco @ gmail com Or Whatsapp him on +1 706 871 4571

br...@gmail.com <br...@gmail.com> #213Jul 30, 2022 11:29AM

UNSUBSCRIBE

Sent from my iPhone

- Show quoted text -

mr...@gmail.com <mr...@gmail.com> #214Jul 31, 2022 05:55AM

UNSUBSCRIBE

ni...@gmail.com <ni...@gmail.com> #215Jul 31, 2022 06:48AM

Unsubscribe

On Sun, 31 Jul 2022 at 07:56, <buganizer-system@google.com> wrote:

- Show quoted text -

--
Nick Verlinde
e: nick.verlinde@gmail.com
m: (+41) 764 011 380

Issue 35875095

Description

Issue summary

Comments

da...@gmail.com <da...@gmail.com> #2Apr 24, 2008 11:24PM

ku...@gmail.com <ku...@gmail.com> #3Jun 15, 2008 10:50AM

mh...@gmail.com <mh...@gmail.com> #4Jun 29, 2008 06:03PM

ma...@gmail.com <ma...@gmail.com> #5Jun 30, 2008 06:11PM

ma...@gmail.com <ma...@gmail.com> #6Jul 1, 2008 11:18AM

wk...@gmail.com <wk...@gmail.com> #7Jul 1, 2008 03:25PM

de...@gmail.com <de...@gmail.com> #8Jul 1, 2008 04:16PM

ro...@gmail.com <ro...@gmail.com> #9Jul 5, 2008 09:13AM

mh...@gmail.com <mh...@gmail.com> #10Jul 5, 2008 06:34PM

co...@gmail.com <co...@gmail.com> #11Jul 9, 2008 02:21PM

de...@gmail.com <de...@gmail.com> #12Aug 25, 2008 06:01PM

ro...@gmail.com <ro...@gmail.com> #13Sep 6, 2008 06:55AM

va...@gmail.com <va...@gmail.com> #14Sep 19, 2008 04:00PM

am...@gmail.com <am...@gmail.com> Sep 25, 2008 10:26PM

tr...@gmail.com <tr...@gmail.com> #15Sep 26, 2008 03:01PM

aj...@googlemail.com <aj...@googlemail.com> #16Sep 26, 2008 06:23PM

ti...@gmail.com <ti...@gmail.com> #17Oct 1, 2008 08:51AM

go...@gmail.com <go...@gmail.com> #18Oct 8, 2008 08:01AM

me...@gmail.com <me...@gmail.com> #19Oct 29, 2008 07:02PM

ed...@gmail.com <ed...@gmail.com> #20Nov 20, 2008 10:39PM

ed...@gmail.com <ed...@gmail.com> #21Nov 26, 2008 05:20PM

bo...@gmail.com <bo...@gmail.com> #22Dec 19, 2008 07:00AM

ja...@gmail.com <ja...@gmail.com> #23Dec 19, 2008 07:07AM

se...@gmail.com <se...@gmail.com> #24Jan 25, 2009 11:49PM

se...@gmail.com <se...@gmail.com> #25Jan 27, 2009 12:47AM

pa...@gmail.com <pa...@gmail.com> #26Jan 27, 2009 07:04AM

hu...@gmail.com <hu...@gmail.com> #27Feb 23, 2009 12:54AM

ch...@gmail.com <ch...@gmail.com> #28Feb 23, 2009 01:04AM

ri...@gmail.com <ri...@gmail.com> #29Feb 25, 2009 01:32PM

ja...@gmail.com <ja...@gmail.com> #30Feb 25, 2009 03:27PM

bj...@gmail.com <bj...@gmail.com> #31Feb 28, 2009 12:31AM

cr...@hotmail.com <cr...@hotmail.com> #32Mar 1, 2009 05:17PM

ro...@gmail.com <ro...@gmail.com> #33Mar 4, 2009 11:47AM

se...@gmail.com <se...@gmail.com> #34Mar 4, 2009 03:17PM

ta...@gmail.com <ta...@gmail.com> #35Mar 4, 2009 06:04PM

ya...@gmail.com <ya...@gmail.com> #36Mar 9, 2009 01:53PM

pa...@gmail.com <pa...@gmail.com> #37Mar 9, 2009 04:13PM

sh...@gmail.com <sh...@gmail.com> #38Mar 9, 2009 04:18PM

go...@gmail.com <go...@gmail.com> #39Mar 10, 2009 04:53PM

tr...@gmail.com <tr...@gmail.com> #40Mar 10, 2009 05:01PM

go...@gmail.com <go...@gmail.com> #41Mar 10, 2009 05:04PM

go...@gmail.com <go...@gmail.com> #42Mar 10, 2009 05:05PM

go...@gmail.com <go...@gmail.com> #43Mar 10, 2009 05:09PM

gr...@gmail.com <gr...@gmail.com> #44Mar 12, 2009 03:41PM

oa...@gmail.com <oa...@gmail.com> #45Mar 13, 2009 12:23AM

he...@gmail.com <he...@gmail.com> #46Mar 15, 2009 03:06AM

pg...@gmail.com <pg...@gmail.com> #47Mar 16, 2009 02:51AM

cp...@163.com <cp...@163.com> #48Mar 17, 2009 01:05AM

la...@gmail.com <la...@gmail.com> #49Mar 17, 2009 09:07PM

[Deleted User] <[Deleted User]> #50Apr 2, 2009 02:43AM

ti...@gmail.com <ti...@gmail.com> #51Apr 6, 2009 10:24AM

ko...@gmail.com <ko...@gmail.com> #52Apr 8, 2009 11:47AM

to...@gmail.com <to...@gmail.com> #53Apr 9, 2009 03:28AM

ed...@gmail.com <ed...@gmail.com> #54Apr 10, 2009 12:32AM

ce...@gmail.com <ce...@gmail.com> #55Apr 15, 2009 12:49PM

ja...@gmail.com <ja...@gmail.com> #56Apr 16, 2009 09:51PM

dr...@gmail.com <dr...@gmail.com> #57Apr 16, 2009 10:06PM

ar...@gmail.com <ar...@gmail.com> #58Apr 17, 2009 07:55PM

ki...@gmail.com <ki...@gmail.com> #59Apr 20, 2009 11:52AM

im...@gmail.com <im...@gmail.com> #60Apr 21, 2009 02:17AM

ar...@gmail.com <ar...@gmail.com> #61Apr 21, 2009 03:10AM

im...@gmail.com <im...@gmail.com> #62Apr 21, 2009 04:00AM

ar...@gmail.com <ar...@gmail.com> #63Apr 21, 2009 04:05AM

ex...@gmail.com <ex...@gmail.com> #64Apr 30, 2009 02:56PM

oz...@gmail.com <oz...@gmail.com> #65Apr 30, 2009 06:20PM

zb...@gmail.com <zb...@gmail.com> #66Apr 30, 2009 07:38PM

wk...@gmail.com <wk...@gmail.com> #67May 2, 2009 09:53AM

ga...@gmail.com <ga...@gmail.com> #68May 8, 2009 11:28PM

wk...@gmail.com <wk...@gmail.com> #69May 9, 2009 09:31AM

sa...@gmail.com <sa...@gmail.com> #70May 9, 2009 08:33PM

ta...@gmail.com <ta...@gmail.com> #71May 9, 2009 11:26PM

wk...@gmail.com <wk...@gmail.com> #72May 10, 2009 10:53AM

md...@gmail.com <md...@gmail.com> #73Jun 10, 2009 05:52PM

wk...@gmail.com <wk...@gmail.com> #74Jun 10, 2009 06:31PM

md...@gmail.com <md...@gmail.com> #75Jun 11, 2009 01:58AM

le...@gmail.com <le...@gmail.com> #76Jun 11, 2009 04:22AM