You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
BigQuery: add destinationTableProperties to LoadJobConfig #5093
@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.
Activity
tseaver commentedon Oct 12, 2018
@tswast while working on this, I am adding unit tests for each of the
LoadJobConfigproperties. I notice thatskipLeadingRowsis mangled to a string in the resource, whilemaxBadRowsis 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.Add explicit test coverage for 'LoadJobConfig.skip_leading_rows'.
Add 'LoadTableConfig.destination_table_friendly_name' property.
tswast commentedon Oct 15, 2018
Per the discovery document (https://www.googleapis.com/discovery/v1/apis/bigquery/v2/rest)
maxBadRowsis an int32 and can safely be represented as an integer in Google's JSON parser.skipLeadingRowsis 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.
Add explicit test coverage for 'LoadJobConfig.skip_leading_rows'.
Add 'LoadTableConfig.destination_table_friendly_name' property.
BigQuery: add destination table properties to 'LoadJobConfig'. (#6202)