Hi Hans, My understanding is that it will truncate the file without respect to the XML structure, resulting in an invalid XML file.
Best, - Eric On Nov 18, 4:42 pm, HK <hravn...@hotmail.com> wrote: > Eric, > > I appreciate you taking the time to look into this. I will let you > know if I see this again. > > One question related to intentional truncation - if AdWords truncates > a report file at 250 MB, will it just omit records at the end so that > the report is still a valid XML file, or will it just chop the file > whenever it hits this limit, likely creating an invalid XML file? I > would prefer the latter so that this scenario will easily be detected > on the caller's side, otherwise it'd be difficult to determine if > records are missing or not. Just curious what the expected behavior > is. I suspect the file will still be valid. > > Thanks > Hans > > On Nov 17, 8:36 am, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > > > Hi Hans, > > > Thank you for the extra information. The truncation does take place > > on the uncompressed size of the report, but a truncation down to 100 > > MB doesn't make sense. The server logs show that there were no errors > > generating the report, so it is unclear what happened. Since we can't > > replicate the issue (the report re-ran successfully) then there is > > little we can do now. Let me know if you see this behavior again. > > > Best, > > - Eric > > > On Nov 16, 8:16 pm, HK <hravn...@hotmail.com> wrote: > > > > Hi, Eric > > > > Our app calls getGzipReportDownloadUrl to get the URL and then > > > uses .NET's WebClient class and DownloadFile method to do the > > > download. It did not fail or error during the download. We run the > > > same report every day (has been for a year), and a few days later, the > > > same report succeeded and ended up being just over 200 MB. The data > > > downloaded in these two reports should be pretty much the same. > > > > As a side note, I understand that AdWords will truncate files over 250 > > > MB (uncompressed I assume). If this truncation occurs, which I don't > > > believe was the case here as it was cut short at just over 100 MB), > > > will AdWords truncate the report in a way so that the XML is still > > > valid, meaning, will it close out the XML elements? > > > > On Nov 16, 3:44 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > > > wrote: > > > > > Hi Hans, > > > > > How does your application download the report? Were there any errors > > > > logged by your application while the report was being downloaded? How > > > > were you able to later verify the full size of the report? > > > > > Best, > > > > - Eric Koleda, AdWords API Team > > > > > On Nov 16, 5:56 pm, HK <hravn...@hotmail.com> wrote: > > > > > > Hi, > > > > > > Last week I received a truncated keyword structure report. It was > > > > > truncated at 109 MB while the full report, which now works fine, > > > > > should've been approximately 216 MB. The report id was 996485045 > > > > > and .NET failed with: > > > > > > System.Xml.XmlException: > > > > > Message: There is an unclosed literal string. Line 3, position > > > > > 114483161 > > > > > > This is the only only time I've seen this, but I'm a little concerned > > > > > this could happen again whenever the circumstances are right. > > > > > > Would it be possible for someone in the AdWords group to take a closer > > > > > look at this? > > > > > > Thanks in advance > > > > > Hans- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=.
