René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"BigQuery: [Primitive-ize API] SchemaField","articleBody":"Consistent with the recent work to allow the API to accept some primitives as well as specific objects, the schema argument to `LoadJobConfig`* could accept a list of dicts. Currently it requires constructing a bunch of `SchemaField` objects:\r\n\r\n```python\r\n\r\n    schema = [\r\n        # could be just column_dicts\r\n        bigquery.schema.SchemaField.from_api_repr(column_dict) for column_dict in column_dicts\r\n    ]\r\n\r\n     with open(empty_path, \"rb\") as source_file: \r\n        job_config = bigquery.job.LoadJobConfig(\r\n            schema=schema, write_disposition=\"WRITE_TRUNCATE\"\r\n        )\r\n\r\n        job = gbq_client.load_table_from_file(\r\n            source_file,\r\n            table_ref,\r\n            location=\"US\",\r\n            job_config=job_config,\r\n        )\r\n```\r\n\r\nWe're trying to move to using the BQ Python API rather than subprocessing out to a shell with `bq`; it's got much better but it's still a bit Java-esque, and these are examples of times it's a tougher sell than constructing a string a sending it to bash. As ever, lmk if the API isn't designed for these cases and you'd encourage users to use bash.\r\n\r\n*this could also be a dict, though less of an imperative.\r\n\r\n","author":{"url":"https://github.com/max-sixty","@type":"Person","name":"max-sixty"},"datePublished":"2019-05-30T16:10:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/8196/google-cloud-python/issues/8196"}