TOOLS-3271 Import Time-Series Collections via mongoimport #535
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.
What
Adds support in
mongoimportfor importing data from CSV & TSV directly into a time-series collection.Today,
mongoimportcan import data into an existing time-series collection, only if it was already created correctly prior to runningmongoimport. However, if there are any issues with the schema, the user will see one error per document. This improvement will fail immediately before trying to insert data so the user can more quickly resolve issues.How
createCollectionwith the user-provided time-series options before inserting.datevia--fields,--fieldFile, or--headerline.autotype is not allowed because adatetype cannot be coerced.datetype will fail on insert, so failing validation prior to insertion is more user-friendly.--columnsHaveTypesis therefore required.API Changes
Four new parameters added:
--timeSeriesTimeField=<column_name>--timeSeriesMetaField=<column_name>--timeSeriesGranularity=[seconds(default),minutes,hours]--timeSeriesExists=[false(default), true]How Tested
Standalone
ReplicaSet
Sharded Cluster
Known Issues
Documents are inserted unordered. I've seen this with the Python driver,
pymongo, when not usingOrderedDict. The Go driver appears to use the orderedbson.Dand not unorderedbson.M, so this is confusing behavior.