Description
This statement is used to create an external table in a database.
An external table is a key feature in a database management system. Generally, a table in a database stores data in the storage space of the database, while an external table stores data in an external storage service.
When you create an external table, you must specify the file path and file format of the data. After that, you can use the external table to read data from the external storage service. An external table is read-only. You can use it in a query statement, but you cannot perform DML operations on it. You cannot define constraints or create indexes on an external table.
Syntax
CREATE EXTERNAL TABLE <table_name>
( [ <column_name> <column_type> [AS <expr>] ]
[ , <column_name> <column_type> [AS <expr>] ]
[ , ... ] )
LOCATION = '<string>'
FORMAT = (
TYPE = 'CSV'
LINE_DELIMITER = '<string>' | <expr>
FIELD_DELIMITER = '<string>' | <expr>
ESCAPE = '<character>' | <expr>
FIELD_OPTIONALLY_ENCLOSED_BY = '<character>' | <expr>
ENCODING = 'charset'
NULL_IF = ('<string>' | <expr>, '<string>' | <expr> ...)
SKIP_HEADER = <int>
SKIP_BLANK_LINES = { TRUE | FALSE }
TRIM_SPACE = { TRUE | FALSE }
EMPTY_FIELD_AS_NULL = { TRUE | FALSE }
)
[ PATTERN = '<regex_pattern>' ]
Parameter description
| Parameter | Description |
|---|---|
| table_name | The name of the external table to be created. |
| column_name | The name of a column in the external table. By default, the data columns in the file are automatically mapped to the definition columns of the external table in order. |
| column_type | The type of a column in the external table. You cannot define constraints such as DEFAULT, NOT NULL, UNIQUE, CHECK, PRIMARY KEY, or FOREIGN KEY in this parameter. |
| AS |
Manually specifies column mappings. When the order of columns in a file is different from that in the external table, you can specify the correspondence between a column in the external table and the Nth column in the file by using the pseudo-column metadata$filecol{N}. For example, c2 INT AS (metadata$filecol4) indicates that the c2 column in the external table corresponds to the fourth column in the file. Note that if you specify manual column mappings, automatic mappings become invalid, and you must define mappings for all columns manually. |
| LOCATION | The path where the external table files are stored. Generally, external table data files are stored in a single directory, which can contain subdirectories. When you create an external table, the table automatically collects all files in the directory.
NoticeWhen you use object storage paths, separate the parameters in the object storage path with |
| FORMAT | The format of external files.
|
| PATTERN | A regular expression pattern that is used to filter files in the directory specified by the LOCATION parameter. For each file in the directory specified by the LOCATION parameter, if the file path matches the pattern, the external table accesses the file. Otherwise, the external table skips the file. If this parameter is not specified, the external table, by default, accesses all files in the directory specified by the LOCATION parameter. The external table stores the list of files that match the PATTERN in the system tables of the database. When the external table is scanned, the list is used to access external files. |
Considerations
- If an external file is deleted, the file no longer exists in the file list when you access the file list. In this case, the external table ignores the missing file.
- If an external file is modified, the external table accesses the latest data of the external file. If the modification of the external file conflicts with a query on the external table, the result of the query may be unexpected. Therefore, avoid modifying the external file while it is being queried.
- If a new file is added to an external directory, the external table does not access the new file. If you want to add the new file to the file list of the external table, you must update the file list of the external table.
Examples
Set the
secure_file_privpath to/home/admin/and place the CSV fileextdata.csvto be imported, in the/home/admin/testdirectory on the local OBServer node that is connected.The following example shows how to set the global secure path.
obclient> SET GLOBAL secure_file_priv = "" Query OK, 0 rows affected obclinet> \q ByeNote
After you set the
secure_file_privvariable to a global variable, you must execute the\qstatement to make the setting take effect.The CSV file contains the following data:
1,'Dave','Smith','d******h@outlook.com','friend',32 2,'Xena','Johnson','x******n@outlook.com','contact',45 3,'Fred','Jackon','f******n@outlook.com','co-worker',19 4,'Alma','Tyler','a******r@outlook.com','friend',53Log in to the database as a user in the tenant and create an external table named
contacts.obclient> CREATE EXTERNAL TABLE contacts ( id INT, firstname VARCHAR(100), lastname VARCHAR(100), email VARCHAR(255), category CHAR(30), age NUMBER ) LOCATION = '/home/admin/test' FORMAT = ( TYPE = 'CSV' FIELD_DELIMITER = ',' FIELD_OPTIONALLY_ENCLOSED_BY ='\'' ) PATTERN = 'extdata.csv';Query data from the
contactstable.obclient> SELECT * FROM contacts; +----+-----------+----------+----------------------+-----------+------+ | id | firstname | lastname | email | category | age | +----+-----------+----------+----------------------+-----------+------+ | 1 | Dave | Smith | d******h@outlook.com | friend | 32 | | 2 | Xena | Johnson | x******n@outlook.com | contact | 45 | | 3 | Fred | Jackon | f******n@outlook.com | co-worker | 19 | | 4 | Alma | Tyler | a******r@outlook.com | friend | 53 | +----+-----------+----------+----------------------+-----------+------+ 4 rows in set