reduce search results size
@jradcliff ya está trabajando en esto.
Desde el 28/6/2022.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Describe the problem you are trying to solve
I migrated from old Adwords API to new Ads API. I recognized that loading some of my reports take longer than before. First I thought it was an server issues, but then I found out that the responses are much larger. An example: when doing the request
SELECT campaign.status, ad_group.status, ad_group_criterion.status, ad_group_criterion.type
FROM ad_group_criterion
WHERE ad_group_criterion.negative = false
AND campaign.status != REMOVED
AND ad_group.status != REMOVED
AND ad_group_criterion.status != REMOVED
on a specific account, the response stream contains 280MB of data. When I did the same request with the old Adwords Reporting API (using GZIPPED_CSV as download format) the download size was only 200KB.
Describe the solution you would like
It would be great if the response size of the Ads API could be similar to the report size of the Adwords API and not differ by a factor of 1400. The old API returned a compressed csv file, the response of the new API seems to be uncompressed. It would be great if the Ads API would communicate to the server using compressed messages.
Describe alternatives you've considered
There is not much I can do on my side, but I hope the library could
- use compressed requests/responses. As far as I could see gRPC supports gzip compression:
io.grpc.stub.AbstractStub.withCompression("gzip")
Additional context
I copied the most of this ticket's content from #438 that I wrote one year ago. The old issue was closed, but only one part of the request was implemented (thanks for that again). @nwbirnie wrote that I should check back in a few months.
- Lenguaje dominante
- Java
- Estrellas
- 211
- Forks
- 188
- Merge medio
- 5 h 16 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de googleads/google-ads-java
-
Catch InvalidArgumentException while GoogleAdsException expected when mutateQuizá libre de nuevo @sarahcaseybot la tomó hace 439 días y no hay ningún pull request abierto. Abiertoquestion
googleads/google-ads-java#852 · 20 comentarios · 1 reacción · 1 asignado ·
-
Partial proxy for GoogleAdsClientQuizá libre de nuevo @jradcliff la tomó hace 497 días y no hay ningún pull request abierto. Abiertoquestion
googleads/google-ads-java#831 · 7 comentarios · 1 asignado ·
-
enhancement question
googleads/google-ads-java#581 · 12 comentarios · 4 reacciones · 1 asignado ·
-
Quickstart guide should not require building the libraryQuizá libre de nuevo @jradcliff la tomó hace 1999 días y no hay ningún pull request abierto. Abiertoenhancement P3
googleads/google-ads-java#342 · 2 comentarios · 1 reacción · 1 asignado ·
Todos los issues de googleads/google-ads-java
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
github/copilot-sdk#2793 ·
Los mantenedores suelen responder en 1 día
-
Unify jpa4 into orm8Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
enhancement good first issue
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100