[
https://issues.apache.org/jira/browse/BEAM-10930?focusedWorklogId=486445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-486445
]
ASF GitHub Bot logged work on BEAM-10930:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Sep/20 00:25
Start Date: 19/Sep/20 00:25
Worklog Time Spent: 10m
Work Description: shollyman commented on pull request #12874:
URL: https://github.com/apache/beam/pull/12874#issuecomment-695136864
Most recent failures appear unrelated to this change, but I'm not familiar
enough with the project to say that definitively.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 486445)
Time Spent: 50m (was: 40m)
> Use dense encoding for BigQuery JSON API interactions
> -----------------------------------------------------
>
> Key: BEAM-10930
> URL: https://issues.apache.org/jira/browse/BEAM-10930
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Seth Hollyman
> Priority: P2
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Did a quick audit of java BigQueryIO, which leverages the underlying
> discovery client for the HTTP interactions with the BigQuery service.
>
> By default, interactions with BigQuery will use pretty-printed JSON responses
> which may include significant whitespace due to the complexity inherent in
> the BigQuery JSON response structure. This whitespace is all unnecessary for
> programmatic interactions, and interactions should use dense encoding as JSON
> is whitespace agnostic.
> Information about the system parameters can be found at the below URL. In
> particular, the prettyPrint parameter governs dense-vs-pretty JSON
> representation.
> [https://cloud.google.com/apis/docs/system-parameters]
>
> I already have a fix for this issue in progress, creating this issue in order
> to submit the PR for review.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
