[
https://issues.apache.org/jira/browse/BEAM-8910?focusedWorklogId=444646&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-444646
]
ASF GitHub Bot logged work on BEAM-8910:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jun/20 00:28
Start Date: 12/Jun/20 00:28
Worklog Time Spent: 10m
Work Description: chamikaramj commented on pull request #11086:
URL: https://github.com/apache/beam/pull/11086#issuecomment-642999491
Based on some offline discussion, I think it's enough to add a single flag
here. We should try to minimize the number of flags we add (add flags is easy
removing is hard).
The main question here I think is regarding preserving backwards
compatibility for users who rely on old behavior. For this purpose a single
flag is enough. Users who need to convert a given type from one form to the
other can easily do that by adding a ParDo. If adding support for a certain
type is beneficial to a lot of users and if there's significant user demand we
can always add that later.
----------------------------------------------------------------
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: 444646)
Time Spent: 16h (was: 15h 50m)
> 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
> Priority: P3
> Time Spent: 16h
> 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)
