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 17:57:02 UTC

[jira] [Updated] (BEAM-8910) Use AVRO instead of JSON in BigQuery bounded source.

     [ https://issues.apache.org/jira/browse/BEAM-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8910:
----------------------------------
    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 AVRO instead of JSON in BigQuery bounded source.
> ----------------------------------------------------
>
>                 Key: BEAM-8910
>                 URL: https://issues.apache.org/jira/browse/BEAM-8910
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Kamil Wasilewski
>            Assignee: Pablo Estrada
>            Priority: P3
>          Time Spent: 19h
>  Remaining Estimate: 0h
>
> The proposed BigQuery bounded source in Python SDK (see PR: [https://github.com/apache/beam/pull/9772)] uses a BigQuery export job to take a snapshot of the table and read from each produced JSON file. A performance improvement can be gain by switching to AVRO instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)