google-cloud-datastore

boolean r = ofy().transact(new Work<Boolean>() { @Override public Boolean run() { Visit visit = ofy().load().type(Visit.class) .filter(Visit.USER_ID, userID) .filter(Visit.VENUE_ID, venueID).first().get(); if (visit == null) return false; visit.setLastRequestDate(new Date(timestamp)); ofy().save().entity(visit).now(); return true; } }); and I get java.lang.IllegalArgumentException: Only ancestor queries are allowed inside transactions. for the line with the get() call. why? I'm only querying Visit entity in this transaction. I'm doing this in a transaction, because I want all this to be

I am a new to Google Cloud Platform. I have setup a Google VM Instance. I am facing an authentication issue on Local Machine while running the command: python manage.py makemigrations Can you please suggest some tips/steps to resolve the same ? Error Trace File "/constants.py", line 18, in <module> table_data = datastore_fetch(project_id, entity_kind) File "/datastore_helper.py", line 23, in datastore_fetch results = list(query.fetch()) File "/venv/local/lib/python2.7/site-packages/gcloud/datastore/query.py", line 463, in __iter__ self.next_page() File "/venv/local/lib/python2.7/site-packages

I would like to know -an example is highly appreciated- How to model relationships in Google App Engine for Java? -One to Many -Many to Many I searched allover the web and I found nothing about Java all guides and tutorials are about Python. I understood from this article that in Python the relationships are modeled using ReferenceProperty . However, I found nothing about this class in the Javadoc reference. Furthermore, in this article they discussed the following: there's currently a shortage of tools for Java users, largely due to the relative newness of the Java platform for App Engine.

I understand that Google AppEngine supports only one inequality filter per query. What are the workaround on this limitation? Are there any solution that will provide similar effect? Actually GAE supports multiple inequality filters as long as they are on the same property . The workarounds to this limitation are data-specific, e.g. it depends how your data is structured and how you want to query it. For example, for geo searching, as @Dan Holevoet mentioned, there are various geo-hashing algorithms. Basically all such algorithms involve combining multiple properties into one and at the same

I have a EntityKind SuggestedInterest. When I populate that with a key "GrpId" and property "suggestedint". Now, I need the "suggestedint" value for a requested "GrpId" So, I write the query as: String findSuggestedInterest(String grpId) { DatastoreService datastore = DatastoreServiceFactory.getDatastoreService(); Filter filter = new FilterPredicate(Entity.KEY_RESERVED_PROPERTY,FilterOperator.EQUAL,grpId); Query q0 = new Query("SuggestedInterest").setFilter(filter); PreparedQuery pq0 = datastore.prepare(q0); Entity result = pq0.asSingleEntity(); return result.getProperty("suggestedint")

Is there anyway of forcing the GAE dev server to keep full text search indexes after restart? I am finding that the index is lost whenever the dev server is restarted. I am already using a static datastore path when I launch the dev server (the --datastore_path option). This functionality was added a few releases ago (in either 1.7.1 or 1.7.2, I think). If you're using an SDK from the last few months it should be working. You can try explicitly setting the --search_indexes_path flag on dev_appserver.py ; it's possible that the default location ( /tmp/ ) isn't writable. Could you post the first