Ad hoc file upload

Ad hoc or one time upload allows you to update files manually to replace table data. This is helpful when you need to replace reference data. The ByteHouse GUI provides an operation wizard to perform the corresponding tasks. Under the hood, ByteHouse loads ad hoc files using the data loading jobs, but it simplifies the process by combining job creation and job execution.

ByteHouse supports the following file types for ad hoc upload:

  • CSV
  • JSON
  • Excel
  • Avro
  • Parquet

You can upload a local file of size up to 200 MB.

Create an ad hoc job

  1. On the data import page, choose New Import Job
1280
  1. Select File from the upload job pop-up
1576
  1. Select a local file to upload, or drag and drop a local file
1280
  1. You can choose an option to specify the format of the file, or you can choose analyse from file to generate schema. Once the schema is generated, you can further adjust it.

For columnar formats such as CSV or Excel, if the file doesn’t have a header, the column names will be in _cX format. To help recognise the columns, there are sample values for reference.

1280
  1. Choose an existing table to import or create a new table. ByteHouse supports custom columns during import, and you can choose not to import columns that are not needed.
1280
  1. Create a name for this ad hoc upload. When done, choose create button to start file loading.
1280

View and edit an ad hoc job

You can find the corresponding file upload job on the Job History page. If you need to reuse the existing configuration to import a new file, you can create an execution job on the file import task details page. Note that for each execution under the same job, the table schema and the file format of the uploaded file should be the same as the original configuration.

2724 2686

To edit the configuration of a job, choose Edit on the job details page and update the column information and target DB/table.

For troubleshooting, you can go to the execution details page and check the loading status and error log for more information.

1280