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
When constructing a Document for analysis, the content can either be raw bytes from the request or a reference to an object in a Cloud Storage bucket (gcsContentUri).
@tseaver What approach have we taken in similar situations where one service "reaches into" another? I could construct a method which accepts a reference to a gcloud.storage.blob.Blob or just accept bucket and object names as strings and construct the gs://{bucket}/{obj} string for the user. WDYT?
Activity
dhermes commentedon Jul 26, 2016
When constructing a
Documentfor analysis, the content can either be raw bytes from the request or a reference to an object in a Cloud Storage bucket (gcsContentUri).@tseaver What approach have we taken in similar situations where one service "reaches into" another? I could construct a method which accepts a reference to a
gcloud.storage.blob.Blobor just accept bucket and object names as strings and construct thegs://{bucket}/{obj}string for the user. WDYT?tseaver commentedon Jul 26, 2016
The BigQuery
LoadTableFromStorageJobis probably the closest equivalent. The other one which is somewhat reltated is the Logging sink to Storage bucket, but there we just pass the user-supplied URI through to the back-end.dhermes commentedon Aug 8, 2016
See #2062
dhermes commentedon Aug 29, 2016
Closed via #2211
chore(deps): bump fiona from 1.9.6 to 1.10.0 in /samples/geography (#…
chore: implement StartsWithOp, EndsWithOp, StringSplitOp and ZfillOp …