0.4 - Support CSV files #29
Merged
Conversation
This file contains 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
…hich can be clobbered by subsequent non-empty values (#26)
…em for JSON, following 'bq load' behavior
…ields in the schema file for CSV input file
Add support for CSV files with header in first row
Infer 'REQUIRED' mode with a flag for consistently filled in values
…n the 'second' field
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
--input_formatflag. Preservethe ordering of fields in the schema file for CSV.
--infer_modeflag for CSV files so that fields that arepresent in all input records are marked as
REQUIREDin the schema(Thanks korotkevics@, see Infer 'REQUIRED' mode with a flag for consistently filled in values #28).