Hi Daniel, thanks for trying out the tool.
We will handle the issues that are created on GitHub, and we can keep the
discussion going there so we have a single point of contact, but because
this wasn't clear before, I am answering your post here so you can keep
track.
First thing to remember,
Hi All,
For any queries, bugs or feature requests on AwReporting, please post them
on the AwReporting github issue
trackerhttps://github.com/googleads/aw-reporting/issues.
This will ensure feedback is handled by the most appropriate team.
Regards,
- Paul, AdWords API Team.
On Friday, 22
Hello, just wanted to point out how disappointing we are with AwReporting
and why.
We were told AwReporting would be the solution to our problems regarding
downloading large scale performance information for all our accounts.
We currently do nightly downloads using the API, calling it in
here is the stack trace:
log4j:WARN No appenders could be found for logger
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
SLF4J: Failed to load class
We are having the same problems.
We have big accounts and the AwReporting tool fails with out of memory
On Thursday, November 21, 2013 11:30:14 AM UTC-3, Daniel Altman wrote:
Hello, just wanted to point out how disappointing we are with AwReporting
and why.
We were told AwReporting would
A couple questions:
Have you tried upping the java heapsize?
Have you considered using the endpoint with Apache HttpClient directly to
download a csv which is supported using the downloadFormat xml element?
Have you considered limiting breaking your reports up into smaller more
reasonably
