You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only foreign elements from the datastore API here are:
DatastoreHelper: returning a property field and a value
c: getting the entity as an input and then outputting another entity.
Shouldn't there be a method to remove, get or set a property by name instead of an int? Adding an existing property produces no error, but saving it to the Datastore service produces an error complaining about a duplicate name for a property.
The text was updated successfully, but these errors were encountered:
In the v1beta3 API, the properties are exposed as an actual map, so this will get a lot simpler once Google Cloud Dataflow is updated to use that API version.
In the meantime, once option is to use DatastoreHelper.getPropertyMap to get the properties as a Map<String, Value>, modify that map as needed, clear the original property list on the Entity.Builder, and then add back the values from the map.
That's what I'm currently doing, but I felt like it could use some improvements. I'll keep following the Dataflow/Beam project as they switch to v1beta3. Thank you very much for the prompt reply @eddavisson .
On Google Cloud Dataflow when adding a property to an entity the process would be
The only foreign elements from the datastore API here are:
DatastoreHelper
: returning a property field and a valuec
: getting the entity as an input and then outputting another entity.Shouldn't there be a method to remove, get or set a property by name instead of an int? Adding an existing property produces no error, but saving it to the Datastore service produces an error complaining about a duplicate name for a property.
The text was updated successfully, but these errors were encountered: