Редактиране

Споделяне чрез


Create an external table using the Azure Data Explorer web UI wizard

An external table is a schema entity that references data stored outside the Azure Data Explorer database. Azure Data Explorer web UI can create external tables by taking sample files from a storage container and creating schema based on these samples. You can then analyze and query data in external tables without ingestion into Azure Data Explorer. For a brief overview, see external tables. For information about different ways to create external tables, see create and alter Azure Storage external tables. This article shows you how to create an external table using the creation wizard experience.

Prerequisites

Create an external table

  1. In the left menu, select Query.

  2. Right-click on the database where you want to create the external table. Select Create external table.

    Screenshot of the option to create an external table from the query page.

The Create external table window opens with the Destination tab selected.

Destination tab

  1. The Cluster and Database fields are prepopulated. You may select a different destination from the drop-down menu.
  2. In Table name, enter a name for your table.

    Tip

    Table names can be up to 1024 characters including alphanumeric, hyphens, and underscores. Special characters aren't supported.

  3. Select Next: Source

Screen capture of the Destination tab with Cluster, Database, and Table name fields.

Source tab

In Link to containers, there are two ways to add a container: Add a container with the Select container button and Add a container with the Add URL or Add container button.

You can add up to 10 source containers.

Add a container with the Select container button

  1. Select Select container.

    Screenshot of select container button in source tab.

  2. Choose the relevant subscription and storage account associated with your container.

    Screenshot of select container window.

  3. Select the Add button. When verification has completed, a green check will appear to the right of the container link.

    Screenshot of verified container link.

Add a container with the Add URL or Add container button

  1. Select the Add URL or Add container button.

    Screenshot of add URL button.

  2. Enter a storage connection strings to your source container with read and list permissions. When verification has completed, a green check will appear to the right of the container link.

    Screenshot of adding SAS URL.

File filters

Use File filters to filter the files that the table should include. Files can be filtered according to folder path, file begins with, or file extension.

Screenshot of selecting schema-defining file.

Schema-defining file

The first source container will display files below File filters.

Screen shot of create external table source tab in Azure Data Explorer.

  1. Choose the schema-defining file by selecting the circle to the left of the file. This file will be used to generate the table schema.
  2. Select Next: schema. The Schema tab opens.

Schema tab

In the right-hand side of the tab, you can preview your data. On the left-hand side, you can add partitions to your table definitions to access the source data more quickly and achieve better performance.

Note

Mappings are not part of the definition of an external table, and are not supported in this wizard. Mappings can be configured later if necessary. Some functionalities, such as deleting the last column in CSV files or changing column names in JSON files, require mappings in order to work correctly.

  1. Select Add partition.

    Screen shot of view file for external table in Azure Data Explorer.

  2. The partition window opens. A partition is defined over a subpath of the file, which can be altered using the Path prefix field. For each partition you wish to apply, fill out the fields as follows:

    Field Description Required/Optional
    Partition name Used for identification of the partition. The name can be arbitrary. Required
    Type The data type of the data partitioning column. Required
    Data column The column used for partitioning. Virtual columns partition according to URL path. Required
    Function The function applied to the data column used for partitioning. Optional
    Function argument Argument to be used in the partition function. Required if function is used.
    Path prefix The subpath of the file on which the partitioning is defined. This prefix changes the URL of the external table, as seen in the Uri preview box, and should match the schema-defining file URI. Optional
    Datetime pattern Format of date that will be used to construct the table URI path. Optional

    Screen shot add partitions to external table in Azure Data Explorer.

    For example, the partition name CustomerName suggests that the value to partition by is in the customer name part of the URL. The above example declared two partitions: one partition over the customer name and one partition over the date embedded in the URL.

    Note

    Virtual columns appear as part of the schema as the columns data extracted from the file path, and this data can be used later in queries.

  3. Select Add partition to add another partition.

  4. Select Save. The partitions you added now appear in the list of Partitions in the left pane. Partitioned columns can't be changed in preview.

    Screenshot of schema external table Azure Data Explorer.

  5. Select Next: Create table. When the table is created, an External table successfully created window opens.

  6. To view the command used to create the table, select View command.

    Screenshot of successful creation of external table in Azure Data Explorer.

  7. To undo the creation of the external table, select Tools > Undo.

Query the external table

The resulting table includes data from all the files that fit the criteria defined above. You can query this table using the external_table() function. For more information on how to query external tables, see Querying an external table.

Screen shot of table output from querying external table in Azure Data Explorer.