google-cloud-datastore

Service error in memcache with Java Google App Engine Standard at random time periods

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-04 13:54:33
In the past month, our Java Google App Engine Standard Web App started getting strange errors at seemingly random times (see stack trace below). Around this time we made the following changes: Switch from Java7 runtime to Java8/Jetty9 runtime (which allowed us more flexibility in linking to a 3rd party payments library). Switch to deploying with the Google Cloud SDK, instead of the separate Google App Engine SDK. Yesterday we experienced 3 periods with errors. One of these occurred from 0530PST to about 0600PST on Feb 28. Suddenly all attempts to load from the database started failing: com

Import large data (json) into Firebase periodically

蹲街弑〆低调 提交于 2019-12-04 13:52:14
问题 We are in the situation that we will have to update large amounts of data (ca. 5 Mio Records) in firebase periodically. At the moment we have a few json files that are around ~1 GB in size. As existing third party solutions (here and here) have some reliability issues (import object per object; or need for open connection) and are quite disconnected to the google cloud platform ecosystem. I wonder if there is now an "official" way using i.e. the new google cloud functions ? Or a combination

Is there a nosql store that also allows for relationships between stored entities?

故事扮演 提交于 2019-12-04 13:14:36
I am looking for nosql key value stores that also provide for storing/maintaining relationships between stored entities. I know Google App Engine's datastore allows for owned and unowned relationships between entities. Does any of the popular nosql store's provide something similar? Even though most of them are schema less, are there methods to appropriate relationships onto a key value store? It belongs to the core features of graph databases to provide support for relationships between entities. Typically, you model your entities as nodes and the relationships as relationships/edges in the

Sending and retreaving data from datastore with mobile backend starter

末鹿安然 提交于 2019-12-04 12:37:30
I'm trying to use Mobile Backend Starter in my Android application. In order to do that I need to store some data in the Datastore. I'm using the provided object CloudEntity but I can only consistently insert and read String . That's the example code I used to send data: CloudEntity entity = new CloudEntity(TEST_KIND_NAME); entity.put(KEY_DATE, new Date(System.currentTimeMillis())); entity.put(KEY_CALENDAR, Calendar.getInstance()); entity.put(KEY_LONG, Long.valueOf(Long.MAX_VALUE)); entity.put(KEY_INTEGER, Integer.valueOf(Integer.MAX_VALUE)); getCloudBackend().insert(entity, simpleHandler);

How to use High Replication Datastore

僤鯓⒐⒋嵵緔 提交于 2019-12-04 12:23:03
Okay, I have watched the video and read the articles in the App Engine documentation (including Using the High Replication Datastore ). However I am still completely confused on the practical usage of it. I understand the benefits (from the video) and they sound great. But what I am lacking is a few practical examples. There are plenty of master/slave examples on the web, but very little illustrating (with proper documentation) the high replication datastore. The guestbook code example used in the Using the High Replication Datastore article illustrates the ancestor key by adding a new

how to update a field value of a data store in google app engine using java

删除回忆录丶 提交于 2019-12-04 12:11:59
问题 I had created a Login (Kind) in the data store. Inside the login, I created two fields username and passsword. When the user changes the password I want to update the field value inside the datastore. but when I used this code, DatastoreService datastore = DatastoreServiceFactory.getDatastoreService(); Entity passwordchange = new Entity("Login"); passwordchange.setProperty("password", "admin@123"); datastore.put(passwordchange); It creates a new row and inserts the password "admin@123"

Trying to store Utf-8 data in datastore getting UnicodeEncodeError

妖精的绣舞 提交于 2019-12-04 11:47:29
Trying to store utf-8 into datastore and getting error : Traceback (most recent call last): File "/sinfo/google_appengine/google/appengine/ext/webapp/__init__.py", line 511, in __call__ handler.get(*groups) File "/sinfo/siteinfo/siteinfo.py", line 1911, in get seoEntity.put() File "/sinfo/google_appengine/google/appengine/ext/db/__init__.py", line 833, in put return datastore.Put(self._entity, rpc=rpc) File "/sinfo/google_appengine/google/appengine/api/datastore.py", line 275, in Put req.entity_list().extend([e._ToPb() for e in entities]) File "/sinfo/google_appengine/google/appengine/api

Following backreferences of unknown kinds in NDB

纵饮孤独 提交于 2019-12-04 11:34:54
问题 I'm in the process of writing my first RESTful web service atop GAE and the Python 2.7 runtime; I've started out using Guido's shiny new ndb API. However, I'm unsure how to solve a particular case without the implicit back-reference feature of the original db API. If the user-agent requests a particular resource and those resources 1 degree removed: host/api/kind/id?depth=2 What's the best way to discover a related collection of entities from the "one" in a one-to-many relationship, given

Cloud Firestore next generation of Cloud Datastore?

浪尽此生 提交于 2019-12-04 11:16:13
问题 I find somewhat contradicting information from Google about which data storage solution I should use for my web app. Since I'm not too interested in using Mobile SDKs and like the server frameworks offered from Cloud Datastore, I would choose that option according to this flowchart. However when I go into my Google Cloud Platform and select the Cloud Datastore option from the menu, I get this message: It raises a lot of questions and confusion. Does this mean that Cloud Firestore will

Cost of storing a file in Datastore vs Blobstore

浪子不回头ぞ 提交于 2019-12-04 11:09:25
问题 Question: Since every file in the blobstore has an associated BlobInfo entity in the datastore, do I get charged the cost of write/read of that entity just like any other datastore entity? Background: We store millions of images on App Engine, and we're currently storing them in datastore entities (the images are smaller than 1MB). I'm wondering if using the blobstore would reduce our cost. I'm not concerned about the cost of storage. The real cost is the act of writing and reading, so that's