|
1 | 1 | ---
|
2 | 2 | title: Use one-click ingestion to ingest data into Azure Data Explorer
|
3 |
| -description: Learn about how to ingest (load) data into Azure Data Explorer simply using one-click ingestion. |
| 3 | +description: Overview of ingesting (loading) data into Azure Data Explorer simply, using one-click ingestion. |
4 | 4 | author: orspod
|
5 | 5 | ms.author: orspodek
|
6 | 6 | ms.reviewer: tzgitlin
|
7 | 7 | ms.service: data-explorer
|
8 |
| -ms.topic: conceptual |
9 |
| -ms.date: 10/31/2019 |
| 8 | +ms.topic: overview |
| 9 | +ms.date: 03/29/2020 |
10 | 10 | ---
|
11 | 11 |
|
12 |
| -# Use one-click ingestion to ingest data into Azure Data Explorer |
| 12 | +# What is one-click ingestion? |
13 | 13 |
|
14 |
| -This article shows you how to use one-click ingestion for quick ingestion of a new table in JSON or CSV formats. The data can be ingested from storage or a local file into an existing table or a new table. Use the intuitive one-click wizard, and your data ingests within a few minutes. Then, you can edit the table and run queries by using the Azure Data Explorer Web UI. |
| 14 | +One-click ingestion enables you to quickly ingest data and automatically suggest tables and mapping structures, based on a data source in Azure Data Explorer. |
| 15 | + |
| 16 | +Using the Azure Data Explorer Web UI, you can ingest data from storage (blob file), a local file, or a container (up to 10,000 blobs). You can also define an event grid on a container for continuous ingestion. The data can be ingested into an existing or new table in JSON, CSV, and [other formats](#file-formats). One click ingestion can suggest a structure for a new table and table mapping, based on the data source, and provide an intuitive platform to adjust the table structure of an existing table and table mapping. One click ingestion will ingest the data into the table within only a few minutes. |
| 17 | + |
| 18 | +One-click ingestion is particularly useful when ingesting data for the first time, or when your data's schema is unfamiliar to you. |
15 | 19 |
|
16 | 20 | ## Prerequisites
|
17 | 21 |
|
18 | 22 | * If you don't have an Azure subscription, create a [free Azure account](https://azure.microsoft.com/free/) before you begin.
|
19 |
| -* Sign in to [the application](https://dataexplorer.azure.com/). |
20 | 23 | * Create [an Azure Data Explorer cluster and database](create-cluster-database-portal.md).
|
21 |
| -* Sign in to the [Web UI](https://dataexplorer.azure.com/) and [add a connection to your cluster](/azure/data-explorer/web-query-data#add-clusters). |
22 |
| - |
23 |
| -## Ingest new data |
24 |
| - |
25 |
| -1. Right-click the *database* or *table* row in left menu of the Web UI and select **Ingest new data (Preview)**. |
26 |
| - |
27 |
| -  |
28 |
| - |
29 |
| -1. In the **Ingest new data (Preview)** window, select the **Source** tab and complete the **Project Details**: |
30 |
| - |
31 |
| - * For **Table**, select an existing table name from the drop-down menu or select **Create new** to make a new table. |
32 |
| - * For **Ingestion type**, select either **from storage** or **from file**. |
33 |
| - * If you selected **from storage**, select **Link to storage** to add the URL. Use [Blob SAS URL](/azure/vs-azure-tools-storage-explorer-blobs#get-the-sas-for-a-blob-container) for private storage accounts. |
34 |
| - * If you selected **from file**, select **Browse** and drag the file into the box. |
35 |
| - * Select **Edit schema** to view and edit your table column configuration. |
36 |
| - |
37 |
| -  |
| 24 | +* Sign in to the [Azure Data Explorer Web UI](https://dataexplorer.azure.com/) and [add a connection to your cluster](/azure/data-explorer/web-query-data#add-clusters). |
38 | 25 |
|
39 |
| - > [!TIP] |
40 |
| - > If you select **Ingest new data (Preview)** on a *table* row, the selected table name will appear in the **Project Details**. |
| 26 | +## File formats |
41 | 27 |
|
42 |
| -1. If you selected an existing table, the **Map columns** window opens to map source data columns to target table columns. |
43 |
| - * Use **Omit column** to remove a target column from the table. |
44 |
| - * Use **New column** to add a new column to the table. |
| 28 | +One-click ingestion supports ingesting a new table from source data in any of the following formats: |
| 29 | +* JSON |
| 30 | +* CSV |
| 31 | +* TSV |
| 32 | +* SCSV |
| 33 | +* SOHSV |
| 34 | +* TSVE |
| 35 | +* PSV |
45 | 36 |
|
46 |
| -  |
| 37 | +## One-click ingestion wizard |
47 | 38 |
|
48 |
| -1. In the **Schema** tab: |
| 39 | +The one-click ingestion wizard guides you through the one-click ingestion process. |
49 | 40 |
|
50 |
| - * Select **Compression type** from the drop-down menu, and then select either **Uncompressed** or **GZip**. |
51 |
| - * Select **Data format** from the drop-down menu, and then select **JSON**, **CSV**, **TSV**, **SCSV**, **SOHSV**, **TSVE**, or **PSV**. |
52 |
| - * When you select the **JSON** format, you must also select **JSON levels**, from 1 to 10. The levels affect the table column data depiction. |
53 |
| - * If you select a format other than JSON, you must select the check box **Include column names** to ignore the heading row of the file. |
54 |
| - * **Mapping name** is set automatically but can be edited. |
55 |
| - * If you selected an existing table, you can select **Map columns** to open the **Map columns** window. |
| 41 | +> [!Note] |
| 42 | +> This section describes the wizard in general. The options you select depend on whether you are ingesting into a new or existing table. |
| 43 | +> For more information, see: |
| 44 | + > * Ingest into [a new table](one-click-ingestion-new-table.md) |
| 45 | + > * Ingest into an [existing table](one-click-ingestion-existing-table.md) |
| 46 | + |
| 47 | +1. To access the wizard, right-click the *database* or *table* row in left menu of the Azure Data Explorer web UI and select **Ingest new data (preview)**. |
56 | 48 |
|
57 |
| -  |
58 |
| - |
59 |
| -1. Above the **Editor** pane, select the **v** button to open the editor. In the editor, you can view and copy the automatic queries generated from your inputs. |
60 |
| - |
61 |
| -1. In the table: |
62 |
| - * Right-click new column headers to **Change data type**, **Rename column**, **Delete column**, **Sort ascending**, or **Sort descending**. On existing columns, only data sorting is available. |
63 |
| - * Double-click the new column name to edit. |
64 |
| - |
65 |
| -1. Select **Start ingestion** to create a table and mapping and to begin data ingestion. |
66 |
| - |
67 |
| -  |
68 |
| - |
69 |
| -## Query data |
70 |
| - |
71 |
| -1. In the **Data ingestion completed** window, all three steps will be marked with green check marks if data ingestion finishes successfully. |
72 |
| - |
73 |
| -  |
| 49 | +  |
74 | 50 |
|
75 |
| -1. Select the **v** button to open the query. Copy to the Web UI to edit the query. |
| 51 | +1. The wizard guides you through the following options: |
| 52 | + * Ingest into an [existing table](one-click-ingestion-existing-table.md) |
| 53 | + * Ingest into [a new table](one-click-ingestion-new-table.md) |
| 54 | + * Ingest data from: |
| 55 | + * Blob storage |
| 56 | + * A local file |
| 57 | + * A container |
| 58 | + * Enter the sample size, from 1 to 10,000 rows (from container only) |
| 59 | + |
| 60 | +1. When you have successfully selected the data source, a preview of the data is displayed. |
| 61 | + If you are ingesting data from a container, you can filter the data so that only files with specific prefixes or file extensions are ingested. For example, you might only want to ingest files with filenames beginning with the word *Europe*, or only files with the extension *.json*. |
76 | 62 |
|
77 |
| -1. The menu on the right contains **Quick queries** and **Tools** options. |
| 63 | +1. Click **Edit schema**. If you are ingesting data into a specific table, you can map the source columns to the target columns and decide whether or not to include column names. |
78 | 64 |
|
79 |
| - * **Quick queries** includes links to the Web UI with example queries. |
80 |
| - * **Tools** includes a link to **Drop commands** on the Web UI, which allow you to troubleshoot issues by running the relevant `.drop` commands. |
| 65 | +1. Start the data ingestion process. |
81 | 66 |
|
82 |
| - > [!TIP] |
83 |
| - > You might lose data when you use `.drop` commands. Use them carefully. |
| 67 | +> [!Note] |
| 68 | +> If your data source is a container, note that Azure Data Explorer's data ingestion aggregation (batching) policy is designed to optimize the ingestion process. By default, the policy is configured to 5 minutes or 500 MB of data, so you may experience latency. See [batching policy](/azure/kusto/concepts/batchingpolicy) for aggregation options. When ingesting data from other sources, the ingestion will take immediate effect. |
84 | 69 |
|
85 | 70 | ## Next steps
|
86 | 71 |
|
87 |
| -* [Query data in Azure Data Explorer Web UI](web-query-data.md) |
88 |
| -* [Write queries for Azure Data Explorer using Kusto Query Language](write-queries.md) |
| 72 | +* Decide if you will use one-click ingestion to ingest data into [an existing table](one-click-ingestion-existing-table.md) or [a new table](one-click-ingestion-new-table.md) |
| 73 | +* [Query data in Azure Data Explorer Web UI](/azure/data-explorer/web-query-data) |
| 74 | +* [Write queries for Azure Data Explorer using Kusto Query Language](/azure/data-explorer/write-queries) |
0 commit comments