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
Copy file name to clipboardExpand all lines: README.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,12 +90,6 @@ You can put a manifest in the same folder with the data files, or you can put it
90
90
- data: local path to the folder that contains the data files to be uploaded
91
91
- manifest: local path to the manifest file
92
92
- id-field: column name in the manifest file that contains file IDs(Keys). Please refer to the data model to determine which property is the ID/Key property.
93
-
- omit-DCF-prefix: for most data commons, this should be set to “false”. One exception is ICDC, which should be set to “true”.
94
-
- name-field: column name in the manifest file that contains data file names
95
-
- size-field: column name in the manifest file that contains data file sizes
96
-
- md5-field: column name in the manifest file that contains data file MD5 checksums
97
-
- id-field: column name in the manifest file that contains data file ID
98
-
- omit-DCF-prefix: boolean to define if need DCF prefix "dg.4DFC"
99
93
- retries: number of retries the CLI tool will perform after a failed upload
100
94
- overwrite: if set to “true”, CLI will upload a data file to overwrite the data file with same name that already exists in the Data Hub target storage. If set to “false”, CLI will not upload a data file if a data file with the same name exists in the Data Hub target storage.
101
95
- dryrun: if set to “true”, CLI will not upload any data files to the Data Hub target storage. If set to “false”, CLI will upload data files to the Data Hub target storage.
0 commit comments