Why isn't an object type named _BlobInfo_ created in the data warehouse when the application is deployed to GAE?

When we upload files to the Blobstore in the Google App Engine, we find that each download creates an entity of the form _BlobInfo_ , which can be seen on the local developer console when viewing the data store in http://localhost:8888/_ah/admin , however after Once the application is deployed to App Engine, such objects are not created when files are uploaded to Blobstore. It seems strange to me, and I wanted to know if something was missing here.

+6
source share
1 answer

_BlobInfo_ not a special name and, most likely, your application does not create objects with this name.

In a production environment, __BlobInfo__ is an internal name for storing information about blobs stored in Blobstore. Note that there are two underscores ( _ ) before and after the word BlobInfo . This object is only created if your application creates and saves blobs in Blobstore.

Since this is an internal object, it is excluded from the Datastore Viewer by default. It is also excluded from the data warehouse statistics page, but they are displayed as BlobInfo under the guise of "All entities."
Using a little trick, you can also show detailed statistics for the __BlobInfo__ object: select any object from the drop-down list, and after reloading the page in the URL, change the kind=XXX parameter to kind=__BlobInfo__ and press Enter, Now the page will reload the statistics for this, even if it hidden from the dropdown list.

However, you can list these objects. For example, go to the Datastore Viewer of your admin console and check "By GQL" so you can enter GQL to list your rights. Now enter the following GQL query:

 SELECT * FROM __BlobInfo__ 

Your BlobInfo objects will be listed BlobInfo .

Note that the Blob Viewer page of your admin console also displays blob based on objects stored as __BlobInfo__ . __BlobInfo__ objects also contain more properties than only those displayed on the Blob Viewer page.

All properties are as follows:

  • ID / Name
  • content_type
  • Creature
  • creation_handle
  • file name
  • md5_hash
  • the size
  • upload_id

They are also available from your application if you have to request these objects.

+4
source

Source: https://habr.com/ru/post/977220/


All Articles