I've implemented Search API, it's wonderful, implementation was easier than
I thought.
However search documents/indexes perish after a SDK restart, I was using
devappserver2's latest version, upgraded to 1.7.7's devappserver2, however
the problem persisted, no matter what I tried, if anyone els
Jason,
Have you thought of using transactional tasks to update the search index?
Or are you more concerned with concurrent updates to the same model?
- Bryce
On Wednesday, April 17, 2013 3:08:05 PM UTC-7, Jason Collins wrote:
>
> We've been doing a fair amount of work with Search API lately. S
Don't know if it would apply to your scenario but it might be a good idea
to update search documents only when the datastore element changes
significantly or gets removed. In my scenario syncing isn't an issue,
however the document rank would change proportionally to the custom rank of
the item
We've been doing a fair amount of work with Search API lately. Some of the
current challenges seem to be around operations aspects. E.g., we're trying
to keep the search documents in sync with datastore entities. Because
transactions don't extend across datastore and search indexes, they can get
