gRPC max message size (#43 continued..) about google-ads-api

[avermeil]

@issacg, regarding the issues not working correctly: make sure you're not running adblock. The name of this repo causes issues with some github features sometimes.

If you're keen to get things working reliably on your end before @kritzware's solution, consider splitting up your request into two: the first with attributes, and the second with segments & metrics. Since you're segmenting by date 30x (I assume?), this will make your response sizes much smaller, since the attributes are wastefully repeated when you segment. You'll need to merge the results of the two requests in your application code (on resource_name), but it sure beats downloading a 9MB payload!

[avermeil]

It turns out that the limit of 4MB was set client side by the node-grpc library that we use. We've raised that limit to 1GB in our latest release, 2.1.1. It's pretty likely that something else will break before you can actually download a 1GB report in a single query, but hey 🤷‍♂

Happy querying!

[kritzware]

Hmm, that's odd. I don't think we have any restrictions on commenting, so perhaps it's an issue on your end? No worries though, we can continue here.

Adding streamed responses is something we are considering for sure. It would be handled in our gRPC library google-ads-node though, where I've opened an issue on this topic. If this works out well, we would most likely implement streaming internally in this library for larger requests, so your code remains the same 👍

[issacg]

Another option, for other stuck here, is to use the pagination controls available via report. It's a bit of a hack, and a bad one too - since you'd need to guess around the payload size of a given page - but it works, and in theory is doing something similar to what streaming would be doing behind the scenes...

(it might be nice to offer page_size via query, too)