Re: [google-appengine] Query Embedded entities

2013-05-05 Thread xybrek
Ok I see, when you say synthetic index, do you mean create a Index kind on a different namespace? Xybrek On Sunday, May 5, 2013 1:42:55 PM UTC+8, Jeff Schnitzer wrote: EmbeddedEntity fields are not indexable. This is mentioned in the javadocs:

Re: [google-appengine] Migrating to Python 2.7 - anything to watch out for?

2013-05-05 Thread Google Tasks Backup Moderator
I can answer your second question - you can have both Python 2.5 and 2.7 versions of your app, as different versions. On 5 May 2013 10:24, NP nearapo...@gmail.com wrote: My app is currently deployed on GAE using python 2.5. I have made changes to the code and it is now running on python 2.7

Re: [google-appengine] Query Embedded entities

2013-05-05 Thread Jeff Schnitzer
No, I mean make up a field in your POJO that _is_ indexed and automatically populate it with the value you want to index. A very crude example is something like this: class Person { // ... String name; @Index String nameNormalized; public void setName(String value) { name =

Re: [google-appengine] Re: Best strategy for near real time updates?

2013-05-05 Thread Pertti Kellomäki
Hi Vinny, Essentially, if you want to push updates in less than a handful of seconds, use the channel API. For anything else, AJAX/JSONP pull updating is completely fine. Thanks for your insight. In my case updates are relatively infrequent and latency is not a big problem, so I guess I'll

Re: [google-appengine] Re: Best strategy for near real time updates?

2013-05-05 Thread Pertti Kellomäki
Hi again Vinny, A related question about implementing pull updates. I would like to pull only the updates since the previous pull, but if possible I would like to avoid recording which updates have been delivered to each client. How much can I trust the datastore timestamps (i.e. auto_now)? The

Re: [google-appengine] Re: Best strategy for near real time updates?

2013-05-05 Thread Jeff Schnitzer
This has come up a number of times in the past. Timestamps are based on the clock on the server running your Python code. Google makes no official guarantees about clock skew in the cluster, although presumably they are all NTP synchronized. In practice, 30s of overlap is going to work 99.9% of

[google-appengine] Mungo API, a Document interface to the GAE Datastore

2013-05-05 Thread Kerby Martino
Due to my requirement to natively store JSON documents into the Datastore I was able to put up a working prototype http://bit.ly/13eSDpr. I called it Mungo, and its is a Document interface to the App Engine Datastore which introduces the concept of DB, DBCollection, and DBObject. It is

[google-appengine] Re: Attention Java MapReduce users

2013-05-05 Thread Eric Jahn
Tom, This is great news. I have one lingering problem as a result of the Files API Bug. Before the Files API fix, I had persisted the file service urls whilst I had been writing to them, and then finalized them successfully. But, because of this bug I couldn't retrieve a blobstore key by

[google-appengine] Google Drive search functionality for GAE ?

2013-05-05 Thread Davy Sitbon
Hi, I'm interesting in storing files in GAE and would like to know if it's possible to index their contents for future search requests without having to decode the content and use GAE search API. As GAE is supposed to give access to technologies used by google products I'm wondering if Google

Re: [google-appengine] Re: Best strategy for near real time updates?

2013-05-05 Thread Pertti Kellomäki
Hi, On Sun, May 5, 2013 at 10:20 PM, Jeff Schnitzer j...@infohazard.org wrote: This has come up a number of times in the past. Timestamps are based on the clock on the server running your Python code. Google makes no official guarantees about clock skew in the cluster, although presumably