Skip to content

Commit 68f2b4c

Browse files
committed
Fixing regions and updating ref article
1 parent 33c3904 commit 68f2b4c

File tree

3 files changed

+7
-21
lines changed

3 files changed

+7
-21
lines changed

articles/storage/blobs/data-lake-storage-query-acceleration-how-to.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article shows you how to use query acceleration (preview) to retrieve a sub
1717
Query acceleration (preview) is a new capability for Azure Data Lake Storage that enables applications and analytics frameworks to dramatically optimize data processing by retrieving only the data that they require to perform a given operation. To learn more, see [Azure Data Lake Storage Query Acceleration (preview)](data-lake-storage-query-acceleration.md).
1818

1919
> [!NOTE]
20-
> The query acceleration feature is in public preview, and is available in the West Central US, Canada Central, and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
20+
> The query acceleration feature is in public preview, and is available in the Canada Central and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
2121
2222
## Prerequisites
2323

articles/storage/blobs/data-lake-storage-query-acceleration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.subservice: data-lake-storage-gen2
1515
Query acceleration (preview) is a new capability for Azure Data Lake Storage that enables applications and analytics frameworks to dramatically optimize data processing by retrieving only the data that they require to perform a given operation. This reduces the time and processing power that is required to gain critical insights into stored data.
1616

1717
> [!NOTE]
18-
> The query acceleration feature is in public preview, and is available in the West Central US, Canada Central, and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
18+
> The query acceleration feature is in public preview, and is available in the Canada Central and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
1919
2020
## Overview
2121

articles/storage/blobs/query-acceleration-sql-reference.md

Lines changed: 5 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.reviewer: ereilebr
1717
Query acceleration supports an ANSI SQL-like language for expressing queries over blob contents. The query acceleration SQL dialect is a subset of ANSI SQL, with a limited set of supported data types, operators, etc., but it also expands on ANSI SQL to support queries over hierarchical semi-structured data formats such as JSON.
1818

1919
> [!NOTE]
20-
> The query acceleration feature is in public preview, and is available in the West Central US, Canada Central, and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
20+
> The query acceleration feature is in public preview, and is available in the Canada Central and France Central regions. To review limitations, see the [Known issues](data-lake-storage-known-issues.md) article. To enroll in the preview, see [this form](https://aka.ms/adls/qa-preview-signup).
2121
2222
## SELECT Syntax
2323

@@ -280,31 +280,17 @@ SELECT weight,warehouses[0].longitude,id,tags[1] FROM BlobStorage[*]
280280

281281
## Sys.Split
282282

283-
This is a special form of the SELECT statement, which is only available for CSV-formatted data:
283+
This is a special form of the SELECT statement, which is only available for CSV-formatted data.
284284

285285
```sql
286286
SELECT sys.split(split_size)FROM BlobStorage
287287
```
288288

289-
In this form, the query returns a list of non-negative integers of sizes of record aligned regions.
289+
Use this statement to get batches of data records from a CSV file. That way you can process records in parallel instead of having to download them all at one time.
290290

291-
### Example
291+
Use the *split_size* parameter to specify the number of bytes that you want the statement to return. For example, if you want to process only 10 MB of data, you're statement would look like this: `SELECT sys.split(10485760)FROM BlobStorage` because 10 MB is equal to 10,485,760 bytes. This statement returns as many records as can fit into those 10 MB.
292292

293-
ABCDEABCD<strong>\n</strong>ABCDEABCDEABCDE<strong>\n</strong>ABCDEAB<strong>\n</strong>ABCDE<strong>\n</strong>ABCD<strong>\n</strong>
294-
295-
The following are examples for the above csv blob:
296-
297-
|Command|Result|
298-
|---|---|
299-
|SELECT SYS.SPLIT(1) FROM BlobStorage<br>SELECT SYS.SPLIT(6) FROM BlobStorage|"10\n16\n8\n6\n5\n"|
300-
|SELECT SYS.SPLIT(7) FROM BlobStorage<br>SELECT SYS.SPLIT(8) FROM BlobStorage|"10\n16\n8\n11\n"|
301-
|SELECT SYS.SPLIT(9) FROM BlobStorage|"10\n16\n14\n5\n"|
302-
|SELECT SYS.SPLIT(10) FROM BlobStorage|"10\n16\n14\n5\n"|
303-
|SELECT SYS.SPLIT(11) FROM BlobStorage<br>SELECT SYS.SPLIT(14) FROM BlobStorage|"26\n14\n5\n"|
304-
|SELECT SYS.SPLIT(15) FROM BlobStorage<br>SELECT SYS.SPLIT(26) FROM BlobStorage|"26\n19\n"|
305-
|SELECT SYS.SPLIT(27) FROM BlobStorage<br>SELECT SYS.SPLIT(34) FROM BlobStorage|"34\n11\n"|
306-
|SELECT SYS.SPLIT(28) FROM BlobStorage<br>SELECT SYS.SPLIT(40) FROM BlobStorage|"40\n5\n"|
307-
|SELECT SYS.SPLIT(41) FROM BlobStorage<br>SELECT SYS.SPLIT(…) FROM BlobStorage|"45\n"|
293+
In most cases, the total bytes returned will be slightly higher than the number that you specify. That's because the **sys.split** function returns complete records only, and a record might start just before the threshold that you specify.
308294

309295
>[!NOTE]
310296
> The split_size must be at least 10 MB (10485760).

0 commit comments

Comments
 (0)