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
{{ message }}
Repository navigation
Draw distinction between bytes in blob_value (datastore property type) and large objects in GCS #329
Per discussion today, we should rollback #263 and document that users should use cloud storage for blobs instead. Quickly scanning the code, another option would be to leave #263 in place but to document that it shouldn't be used for large byte strings and to potentially raise an error over a certain size. ISTM the code would fail if we tried to insert a blob that is large enough (10MB?).
True blob support is really an artifact of the old datastore implementation (just like GQL) which predates Cloud Storage.
I don't know if we have non-docstring docs for working with Entities, but some kind of "narrative" summary that covered them, poiting at the API docs for the concepts would be good. Showing how one might use storage for blob data, tracking keys in datastore, would be useful there.
changed the title [-]Remove support for blob_value and document preferred usage[/-][+]Draw distinction between bytes in blob_value (datastore property type) and large objects in GCS[/+]on Nov 12, 2014
Activity
dhermes commentedon Nov 3, 2014
UPDATE: From docs https://cloud.google.com/datastore/docs/concepts/entities a blob_value should be explicitly kept small.
tseaver commentedon Nov 12, 2014
I don't know if we have non-docstring docs for working with Entities, but some kind of "narrative" summary that covered them, poiting at the API docs for the concepts would be good. Showing how one might use
storagefor blob data, tracking keys indatastore, would be useful there.dhermes commentedon Nov 12, 2014
I agree. May also be possible to point to existing docs with concepts.
FWIW I'm not sure this bug is valid as currently named. It may be worthwhile for storing bytes in the datastore, just not files, images, etc.
tseaver commentedon Nov 12, 2014
Maybe change the title to "Document storing only small blobs in 'blob_value'"
[-]Remove support for blob_value and document preferred usage[/-][+]Draw distinction between bytes in blob_value (datastore property type) and large objects in GCS[/+]dhermes commentedon Nov 12, 2014
I went a bit more verbose, WDYT?
tseaver commentedon Nov 12, 2014
Sounds fine.
dhermes commentedon Jan 27, 2015
Closing this and folding into #532 since the
documentation is sufficient.
Implementation of get_schedule (get_availability) as requested on goo…
29 remaining items
fix: Add support for Python 3.11 (#329)
chore(deps): update all dependencies (#329)
fix: resolve issue where pre-release versions of dependencies are ins…
chore(main): release 2.7.1 (#329)
chore: remove unused files (#329)
chore: update precommit hook pre-commit/pre-commit-hooks to v4 (#1083) (
fix: fix race condition in remote calls (#329)
chore: update precommit hook pre-commit/pre-commit-hooks to v4 (#1083) (
chore(deps): update all dependencies (#329)
fix(sample): retry InternalServerError (#329)
fix: Remove EXPERIMENTAL tag for ordering keys in publisher/client.py (…
fix: Use unittest.mock (#329)
fix: Add `existing_nullable` usage to `visit_column_type` (#329)
chore: add SECURITY.md (#329)
build(deps): bump markdown-it-py from 2.1.0 to 2.2.0 in /.kokoro (#329)