NDB Compressed properties compatibility #4082

Activity

1. dhermes commented on Sep 29, 2017

   

   dhermes

   on Sep 29, 2017

   Contributor

   More actions

   @cpavon I'm pretty sure ndb sets a meaning on the property, which is a "bygone" feature of the datastore API (i.e. not officially supported). Can you retrieve the raw protobuf contents of each property and let me know the difference (I think it'd be faster than me deploying a GAE app)?

   >>> from google.cloud import datastore
   >>>
   >>> client = datastore.Client()
   >>> key1 = client.key('Foo', 'Bar')
   >>> key2 = client.key('Foo', 'Baz')
   >>>
   >>> key_pbs = [key1.to_protobuf(), key2.to_protobuf()]
   >>> lookup_response = client._datastore_api.lookup(
   ...     client.project, read_options=None, keys=key_pbs)
   >>> lookup_response
2. dhermes

   added

   api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.

   on Sep 29, 2017
3. cpavon commented on Oct 2, 2017

   

   cpavon

   on Oct 2, 2017

   Last edited by cpavon

   Author

   More actions

   Yep, you're right, the value stored using NDB arrives with meaning "22".

    properties {
         key: "name_compressed"
         value {
           meaning: 22
           blob_value: "x\234+I-.\001\000\004]\001\301"
           exclude_from_indexes: true
         }
       }
   

   And everything works fine if I set the proper meanings before the put operation using the API:

   datastore_entity._meanings = {'name_compressed': (22, datastore_entity.get('name_compressed'))}
   client.put(datastore_entity)
   

   If I save the entity in that way NDB and API are be able to read it without problems.

   Is that the right way to set the meanings?
4. dhermes commented on Oct 2, 2017

   

   dhermes

   on Oct 2, 2017

   Contributor

   More actions

   We don't "officially" support meanings. The non-public attribute _meanings is there so that we don't wipe meanings when put-ing an existing entity that has been updated.

   Though we don't "officially" support it, you have identified a working code path so feel free to use it. The fact that _meanings is non-public means we may remove, rename or relocate it at any time.

   I'm going to close this issue out, let us know if you need anything else?
5. dhermes

   closed this as completedon Oct 2, 2017
6. JustinBeckwith

   assigned

   dhermes

   on Feb 1, 2021
7. parthea

   added a commit that references this issue on Oct 21, 2023

   move monitoring samples from python-docs-samples (#51)

   ...

   d95f563