Skip to content

BigQuery: add destinationTableProperties to LoadJobConfig #5093

Closed

Description

@yan-hic

Activity

  1. added
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    api: bigqueryIssues related to the BigQuery API.
    on Mar 22, 2018
  2. self-assigned this
    on Oct 12, 2018
  3. tseaver commented on Oct 12, 2018

    @tseaver
    Contributor

    @tswast while working on this, I am adding unit tests for each of the LoadJobConfig properties. I notice that skipLeadingRows is mangled to a string in the resource, while maxBadRows is not. Which is correct? Given that we are using JSON, and the numbers expected wouldn't be huge, I would think that leaving them both as integers would be correct. The docs show them both as integers.

  4. tswast commented on Oct 15, 2018

    @tswast
    Contributor

    Per the discovery document (https://www.googleapis.com/discovery/v1/apis/bigquery/v2/rest)

    maxBadRows is an int32 and can safely be represented as an integer in Google's JSON parser.

    skipLeadingRows is an int64, so needs to be encoded as a string for Google's JSON parser.

    I asked the BigQuery team this same question (why the inconsistency in types) and they didn't have a satisfactory answer.

  5. added a commit that references this issue on Oct 17, 2018
    cf806f2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the BigQuery API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions