Anyone know what the current limits for writing are per worker invocation? Say I wanted to do ~450..
Anyone know what the current limits for writing are per worker invocation? Say I wanted to do ~450... would that be viable? 
Joh neat
Sthere are limits at the moment
SSwe do have limits for how many times you can write from a single worker invocation -- we should document what that isI don't think it's been documented yet but ItsJulian was limited to 100
SI don't think so, I think it means you will start getting sampled responses from queries
Slike count() won't return the exact number but an approximate
Syeah
SI remember someone asked that before
Strying to find it
Syeah probably lol, couldn't find it 
Sah yep
SI'm keen on being able to delete data still 
using google's bigquery till that happens
using google's bigquery till that happens
Syeah lol
S
Snegative
SJIt throws once you hit 26 writes
W*in a single request cycle
WBro what are you doing 
Sthat’s so cool 
Sif you don’t mind sharing, what sort of model is that?
UOut of curiosity how does the sampling work? Especially curious how it might affect tracking an APIs latency if the data starts getting sampled.
UI'm pretty sure they do write sampling in some way and not using the select sampling
Soh ok, curious to find out more about it
SUInteresting, is it already possible to create indexes based on a customer id? Or is that 
Sthanks! makes a lot of sense
S
Sbeats this mess lol
WBreaking changes are ok as long as they're announced beforehand 