Overview
Local files are uploaded to tables to parse local structured and semi-structured files into structured data tables, which are then stored in a specified Schema under the Catalog (data catalog). After the upload is complete, the table can be searched in the data catalog and can be directly used for SQL queries, dashboards, and downstream task processing. The entry card in the console is named Upload File to Table. It opens as a drawer on the right, and the overall workflow is "Select File → Preview Data and Confirm Schema → Storage Settings → Create Table".
Applicable Scenarios
One-time data analysis: Directly create tables from manually organized sales tables, inventory tables, reconciliation files, and other data for temporary analysis.
Quickly load sample data into the lake: Load small-scale sample data into tables to verify SQL logic or build dashboard prototypes.
Scattered files without modeling: When source data consists only of files and no connectable database is available, tables are generated directly from the files.
Prerequisites
Condition | Description |
Data Integration Permission | |
Computing Resource | Available interactive cluster computing resources exist in the current Workspace for parsing files and creating tables. For details, see Create Computing Resources. |
Target Catalog and Schema | Have write permission on the target Catalog and Schema. If no available Schema exists, create one immediately in the storage settings step. |
File to Upload | |
Use Limits
Limit | Description |
File Type | CSV, JSON, Avro, Parquet, Text, and XML, with corresponding extensions .csv, .json, .avro, .parquet, .txt, and .xml |
Number of files | At least 1 and up to 10 files per operation, with mixed types allowed. |
File Size | Total size of all files does not exceed 2 GB. |
Preview Rows | Data preview displays up to 50 rows. |
Operation Steps
Step 1: Entering File Upload to Table
1. Log in to the DataBuddy console and switch to the target Workspace.
2. Select Data Integration in the left sidebar and confirm that you are on the Access Method Tab.
3. In the File area, click the Upload File to Table card. The system opens the Upload File to Table drawer on the right.
Step 2: Selecting a Local File
Two methods are supported for adding files:
Drag and drop: Drag files directly to the file upload area in the drawer.
Click to select: Click Select File to select one or more files in the system file browser.
Note:
When the number of files or the total size exceeds the limit, the page displays a non-blocking message that disappears automatically after a few seconds. Files exceeding the limit are not added to the list. Split or reduce the files and try again.
Step 3: Selecting a Service Resource
The service resource is used to parse uploaded files and create tables, and it is a required option.
Parameter | Description | Required | Default Value |
Service resources | Single choice. The drop-down list displays only interactive cluster compute resources that the current account has permission to use, and shows the current status of the resources. | Yes | - |
After you select a resource, the page displays the creator and resource type. Click Details to open the compute resource details page in a new tab.
If the selected resource is not started, the system automatically starts it before parsing the file.
Tip
Compute resources are billed based on actual usage. For resource specifications and the automatic start/stop policy, see Compute Resource Overview. Step 4: Previewing Data and Confirming the Schema
After the file is uploaded, you automatically go to the Data Preview step. The system first writes the file to the lakehouse and then parses it. After parsing is complete, the preview table displays data samples, and all operations become available again.
In this step, you need to confirm the following:
1. Confirm the table name: The table name cannot be the same as an existing table.
2. Confirm fields: Select the fields to be stored, and modify the field names, field types, and DECIMAL precision as needed. Keep at least one field.
3. To correct parsing rules: Click Advanced Settings and adjust the delimiter and row tag parsing parameters based on the file type.
Note:
Modifying Advanced Settings triggers reparsing, and manually adjusted field names and field types may be reverted to the system-inferred results. It is recommended to stabilize the parsing rules before editing fields.
Step 5: Storage Settings
After confirming the preview results, go to the Storage Settings step to specify the storage location for the table and the handling method for tables with the same name.
Parameter | Description | Required | Default Value |
Target Location | Select Catalog and Schema in the directory tree. The table will be created under the selected Schema. Only directories that you have permission to access are displayed. | Yes | - |
Solution | Overwrite with same name: overwrite the existing table with the same name using the current data; Create a copy: create a new table named "TableName_1". | Yes | - |
The directory tree supports searching for catalogs and schemas by keyword.
When you hover over a catalog, + Schema appears on the right. Click it to create a Schema directly without exiting the current process.
Click Data Catalog to browse the complete data catalog in a new tab.
Warning
Selecting "Overwrite with the same name" replaces the original data in the target table with the data uploaded this time, and the overwritten data cannot be recovered. To retain the original table data, select "Create a new copy".
Step 6: Creating a Table and Verifying the Result
1. Click Create Table. During table creation, all options in the current step are unavailable.
2. After the table is created successfully, the page automatically redirects to the location of the table in Data Catalog. 3. In the data catalog, confirm that the table has been generated and that the fields are as expected. You can then query the table using SQL. For metadata management of the table, see Data Catalog Overview. Reusing the Most Recent Upload
When you open the "Upload File to Table" drawer, if you have a successfully submitted upload record within the last 24 hours, the page prompts you with the most recently uploaded file. Click Preview File to reuse that batch of files and continue with the subsequent steps without reselecting local files.
Feature | Description |
Validity period | 24 hours; records are no longer displayed after expiration. |
Visibility scope | Only the current account's own upload records are displayed; upload records of other members are not displayed. |
FAQs
Q: What should I do if a single upload exceeds 10 files or the total size exceeds 2 GB?
A: Upload data in multiple batches. If the data volume is large or periodic ingestion is required, use File to Table Sync to process data through offline sync tasks. Q: Can multiple files with inconsistent fields be merged into a single table?
A: Yes. In table merge mode, the system takes the union of fields from all files, and data rows missing a field are filled with null. If the file structures differ significantly, it is recommended to use separate table upload to avoid generating a large number of empty fields.
Q: Will nested structures in JSON and XML be expanded into multiple columns?
A: No. Nested content is parsed as a single text field. To break it down, you can process it with SQL functions after loading it into the table. For details, see File Parsing and Inference. Q: Will field names change after table creation if the source file field names are in Chinese?
A: Yes. The system automatically normalizes field names by converting Chinese characters to pinyin and replacing illegal characters with underscores. You can manually change them to the desired names in the Data Preview step. For details about the rules, see Supported File Types and Constraints. Q: Can the table structure be adjusted after upload?
A: Field adjustments after table creation must be completed in the data catalog or through SQL tasks. If only the parsing of this upload is incorrect, it is recommended to correct it in the Data Preview step and then recreate the table.
Q: What should I do if "No permission to perform the upload service" is displayed?
A: This usually occurs when permissions for the Data Integration module or compute resource usage have changed. Contact your administrator to verify the permission configuration. For details, see Member and Permission Management. References