[google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

Thanks, Chad. Re your comment about caching, I am using NDB on the Python side, which I thought used memcache automatically. So I guess I am using caching, but I thought that modules in the same project (mine are) shared memcache. Is that not true if one module is Python and the other Java?

[google-appengine] Channel API alternatives

It would be great if google could provide a porting guide at the least. I also agree that once you got them working they're great, wasn't so happy to hear they're out the window. Why couldn't you just move the infrastructure underneath to share firebase tech instead of gtalk and leave it

[google-appengine] Re: Backing up AppEngine

I think it would be great if GAE had better support for restoration of accidental deletes. For example, if you could store a unique Id for a transaction and somehow undo all the writes/deletes later. That would be great. Given the nature of distributed systems, and the complexity required in

[google-appengine] Re: Backing up AppEngine

I think it would be great if GAE had better support for restoration of accidental deletes. For example, if you could store a unique Id for a transaction and somehow undo all the writes/deletes later. That would be great. Given the nature of distributed systems, and the complexity required in

Re: [google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

I don't believe I use Objectify, unless it's used transparently by the Java Datastore API. Here's a snippet of code that shows how I use the API: DatastoreService datastore = DatastoreServiceFactory.getDatastoreService(); Key key = KeyFactory.stringToKey(serKey); try { Entity entity =

Re: [google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

I now think that caching shouldn't be an issue. When I write an entity on the Python side, NDB invalidates the entity's cache entry (according to the docs), forcing (strongly consistent) reads to get the value from the Datastore service. So a lookup-by-key read from the Java side should get

Re: [google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

There is no standard way of storing entities in memcache. Objectify uses its own namespace and uses the string version of Keys as the cache key. I don’t know what NDB does. Cache invalidation is already a hard problem (that and naming things, as they say). If you want to access data from both

Re: [google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

Just to be 100% clear (sorry I keep double-posting, it's a bad habit): Java and Python modules in the same app share Memcache, which is just a giant Key-Object map. Objectify uses different Memcache keys than NDB. I don't remember Ofy's format, and can't find NDB's, so let's just say

[google-appengine] Re: Channel API alternatives

I was just discussing this very point with someone today. Firebase and Channel are not equivalent, which is why Google appears to be pushing this API change. Otherwise what is the point of having API, if implementation details cannot be addressed seamlessly? On Monday, October 31, 2016 at

Re: [google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

> When I write an entity on the Python side, NDB invalidates the entity's cache entry (according to the docs), I think you missed the *key* part of Jeff's response. Objectify and NDB do not use the same entries in Memcache. So while NDB on Python invalidated *its* cache entry, Objectify used

[google-appengine] Re: Cached Requests

As far as we were able to find, this post and the bug report below are still the defacto and best documentation for GAE Edge Caching on the internet, 5 years later... If someone else has a more complete and up to date Docs link or blog post, please let me know. Michael Prentice GDG Space Coast

[google-appengine] Can't remove custom domains from App Engine projects

Hello, I want to remove some custom domains from one project and add them to another project. I know, that I was able to remove custom domain before. Now I only get the message (translated from German): Only domain owners are permitted to remove an assignment And the delete button is greyed

[google-appengine] Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

Hi, We have an app wherein a Datastore entity is written to by a Python module (using NDB), and then in an immediately following request, read from, using the entity's key, by a Java module. In a situation where the app was heavily loaded, it seemed like the Java module was reading stale data.

[google-appengine] Re: 403 Forbidden for some clients/unable to connect

Hey Folks, If anybody could capture the requests and response of a consistently-failing link (what Evan has said about certificates, HTTPS and static file paths is interesting) using wireshark , using HAR capture

[google-appengine] Re: Backing up AppEngine

Hello Joshua, Protecting against human error is important, we all agree on that. You mention your production project along with test projects. The platform allows granting various levels of access to team members; IAM lets you adopt the security principle of least privilege, so you grant

Re: [google-appengine] Re: 403 Forbidden for some clients/unable to connect

I think I figured out my issue: Our customer has a corporate firewall that appears to be blocking *.appspot.com. Probably due to "security" concerns (see following). Our workaround is to just use our custom domain everywhere instead. For whatever reason, they don't block that.

[google-appengine] Re: AppEngine (AppInventor TinyWebDb application) access from a python local application

Hello Christian, The link provided in my initial reply referred erroneously to creating an app in the cloud, not to a Python client; I correct it here . For your N° 1 solution, you may consider the App Engine Python API

[google-appengine] Re: Can't remove custom domains from App Engine projects

Hello Sven, Does the user have the proper permissions, when you try to remove the custom domain names? You mention only one account. Is this user account the one who attached the custom domain names initially? This condition needs to be fulfilled, for it to be able to remove the same custom

[google-appengine] Unable to upload images on my webpage deployed in google app engine.

Hi, I deployed static webpages on google app engine but it wont load jpg files on one of the pages. This is how my page looks currently. All my other images on other

[google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

Also, make sure you aren't doing deferred writes or starting the Java request before your Python transaction closes. On Monday, October 31, 2016 at 2:05:06 PM UTC-5, Chad Vincent wrote: > > Yes. Consistency is handled by the database layer, not the application > runtime. > > HOWEVER, if you

[google-appengine] Re: Is Datastore lookup-by-key strongly consistent when write is done in Python module and read is done in Java module?

Yes. Consistency is handled by the database layer, not the application runtime. HOWEVER, if you are caching entities (Objectify, etc.) you either need to ensure your Memcache keys are identical or disable caching for those entities. Otherwise the Java cache may return a stale result because

[google-appengine] Re: java.lang.IllegalArgumentException: operating on too many entity groups in a single transaction.

Hey V.B, For now it appears this will need to be simply included as a constant in your application. You can update the constant if in future you notice that the value has changed. These changes are announced in the release notes for the SDK .

[google-appengine] Re: Unable to delete a key from memcache - App engine shows 'Deleting' for a very time

If this occurs again, I'd advise doing the following: 1) Get a header file capture as a HAR file while reproducing the issue in the Cloud Console. 2) Open an issue on the googleappengine public issue tracker