umm, just so you know the report was not compressed.. I got an uncompressed report- but I requested it over an zip-http connection (whether or not this was actually executed this way, only curl knows)
The report size was about 403m.. I don't have it around anymore unfortunately.. (I didn't mean to request that date range).. -tim On Sep 16, 3:42 pm, AdWords API Advisor <[EMAIL PROTECTED]> wrote: > Hello Tim, > > Do you happen to have the size of the original gzip-ed download > handy? Or if you have the 400mb report still around, could you gzip it > (with the default compression level, I guess) and let me know what the > compressed size is? > > There are some limitations that are probably coming into play here on > the size of the file that actually gets transferred to your HTTP > client, but they would apply to the size of the gzip-ed file, not the > uncompressed report size, so I'm interested in finding that out. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Sep 13, 10:30 am, timprepscius <[EMAIL PROTECTED]> wrote: > > > xml over zip http connection.. > > > On Sep 12, 4:08 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > wrote: > > > > An update: the consensus is that while this truncating behavior was > > > known, it wasn't really intentional--there's no explicit hard limit on > > > reports size in the AdWords API or the reports center, and the > > > behavior is due to an infrastructure dependency. I'm afraid that I > > > can't go into too much detail about what's going on under the hood, > > > but the takeaway is that we have some folks looking into whether > > > anything has changed in the relevant infrastructure recently that > > > might have increased the maximum download size. Once we have a good > > > answer for that we'll get the limits added to the documentation once > > > and for all. > > > > Tim, could you clarify whether the 400 megabyte report was downloaded > > > as a raw XML document, or a gzipped file? If it was initially gzipped, > > > how large was the gzip archive? > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Sep 11, 11:34 am, AdWords API Advisor > > > > <[EMAIL PROTECTED]> wrote: > > > > Hello Tim, > > > > > Looking back in the archives of this group, it looks like that cut- > > > > off has always been something of a mystery, with empirical tests > > > > placing it at around 260 megabytes for the uncompressed report. I > > > > haven't heard anything myself, so I'll see what I can do to get an > > > > official word about this from the engineering team and have it > > > > documented somewhere if there is still a hard limit or if there is any > > > > sort of dynamic cutoff now. > > > > > Cheers, > > > > -Jeff Posnick, AdWords API Team > > > > > On Sep 10, 3:38 pm, timprepscius <[EMAIL PROTECTED]> wrote: > > > > > > I just did a report that's >400 megabytes.. So obviously the old cut > > > > > off does not apply.. > > > > > Is there a cut off? > > > > > > Thanks! > > > > > > -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
