Nested schema object in a fields key#22
Closed
bartlinga wants to merge 1 commit into
Closed
Conversation
Owner
|
@aronb This requires unit test updates (https://travis-ci.org/tylertreat/BigQuery-Python/builds/34303906) FYI @aneilbaboo |
Author
|
Ah, let me get familiar with Travis CI and try again. Should be simple enough. |
Owner
|
The Travis build will run automatically when you push to the PR. You should On Wed, Sep 3, 2014 at 11:28 AM, Aron Bartling [email protected]
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When loading data from a uri the job object was not being formed properly. The schema object was not nested within a fields key. I've added this nesting which is the same approach as used with the create table method.