You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:01:02 UTC
[jira] [Updated] (BEAM-10930) Use dense encoding for BigQuery JSON
API interactions
[ https://issues.apache.org/jira/browse/BEAM-10930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-10930:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.
> 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
> Assignee: Seth Hollyman
> Priority: P2
> Time Spent: 2h
> 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)