3 ms·
And it would have been pretty simple to run a query for users with over 4 million objects, and fire off an email to them all saying "We are about to implement a
by londons_explore 4y ago
And it would have been pretty simple to run a query for users with over 4 million objects, and fire off an email to them all saying "We are about to implement a limit, and you will be impacted. Here are potential workarounds/mitigations".
I suspect though that the simple process of dropping a few hundred customers who will be directly impacted an email requires approval from 27 middle managers, and it's easiest to just ignore them.
- shadowgovt 4y agoMore often, this kind of error out of Google comes from the left hand not knowing what the right hand is doing. Joe or Jane Noogler has just been brought into the team, and their starting project was to improve indexing. They succeeded in doing so by attaching the Drive data to an indexing service created after Drive existed. It's working great and has a 10-20X speedup. But oops... That new indexing system has a 5-million-element hard limit built in, and nobody caught it until they went to production. J. Noogler is too new to have realized this could have been an issue so they never started the escalation / customer messaging processs.