René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"job.py in bigquery does unnecessary client-side validation of data formats","articleBody":"The BigQuery engineering team may decide to expand the allowed formats for import and export, but the allowed values are hard-coded client side. Imports are limited to CSV, DATASTORE_BACKUP, NEWLINE_DELIMITED_JSON, AVRO, for example.\r\n\r\nThis means that if the BigQuery starts to allow other formats, users will be unable to use those new formats without updating their client. Moreover, there is no way for BigQuery to roll out new formats to a whitelisted set of users. \r\n(note this is not mere idle speculation and is currently impacting real users alpha testing a new format)\r\n\r\nSee code here:\r\n[https://github.com/GoogleCloudPlatform/google-cloud-python/blob/master/bigquery/google/cloud/bigquery/job.py#L116][1]\r\nand \r\n[https://github.com/GoogleCloudPlatform/google-cloud-python/blob/master/bigquery/google/cloud/bigquery/job.py#L139][2]\r\n\r\n[1]: https://github.com/GoogleCloudPlatform/google-cloud-python/blob/6d7fae96d25a0a468683a5ab25a2f48014a16378/bigquery/google/cloud/bigquery/job.py#L116\r\n[2]: https://github.com/GoogleCloudPlatform/google-cloud-python/blob/6d7fae96d25a0a468683a5ab25a2f48014a16378/bigquery/google/cloud/bigquery/job.py#L139","author":{"url":"https://github.com/jtigani","@type":"Person","name":"jtigani"},"datePublished":"2017-08-04T17:27:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/3725/google-cloud-python/issues/3725"}