tvalentyn commented on pull request #11086:
URL: https://github.com/apache/beam/pull/11086#issuecomment-634324376


   @pabloem, would you mind squashing the commits that happened after the last
   review iteration (but please don't squash earlier commits until review is
   finalized) and resolving any comments that are already addressed? You can
   also delete the "Run postcommit..." which would make  it easier to follow
   up on remaining comment threads.
   
   On Thu, May 21, 2020 at 12:52 PM Pablo <[email protected]> wrote:
   
   > *@pabloem* commented on this pull request.
   > ------------------------------
   >
   > In sdks/python/apache_beam/io/gcp/bigquery.py
   > <https://github.com/apache/beam/pull/11086#discussion_r428877884>:
   >
   > > @@ -610,7 +611,8 @@ def __init__(
   >        coder=None,
   >        use_standard_sql=False,
   >        flatten_results=True,
   > -      kms_key=None):
   > +      kms_key=None,
   > +      use_json_exports=False):
   >
   > Restarting this discussion after some rebasing and preparing...
   >
   > I think I'd prefer to allow users to choose the export file format. This
   > is what we do for writing to BQ in Java and Python. Allowing users to
   > choose output type for specific column types would add overhead of (if avro
   > and json_format_bytes: formatbytes; if avro and json_datetime_format:
   > formatdatetime; if not avro and not json_format_bytes: formatbytes; ...).
   >
   > We can discourage users from using JSON (AVRO is already the default) -
   > and eventually stop supporting it if that makes sense. Thoughts?
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/beam/pull/11086#discussion_r428877884>, or
   > unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/ACHZCYCRXV5WRILNRQP2IZDRSWBA3ANCNFSM4LESJLFQ>
   > .
   >
   


----------------------------------------------------------------
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]


Reply via email to