Skip to content

Commit a7a92d0

Browse files
authored
Merge pull request #106413 from sangling/patch-2
Corrected DateIime to DateTime
2 parents fd99968 + 4286fab commit a7a92d0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/synapse-analytics/data-explorer/data-explorer-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ The implementation of the index depends on the type of the field, as follows:
6464
| Field type | Indexing implementation |
6565
| -- | -- |
6666
| **String** | The engine builds an inverted term index for string column values. Each string value is analyzed and split into normalized terms and an ordered list of logical positions, containing record ordinals, is recorded for each term. The resulting sorted list of terms and their associated positions is stored as an immutable B-tree. |
67-
| **Numeric**<br />**DateIime**<br />**TimeSpan** | The engine builds a simple range-based forward index. The index records the min/max values for each block, for a group of blocks and for the entire column within the data shard. |
67+
| **Numeric**<br />**DateTime**<br />**TimeSpan** | The engine builds a simple range-based forward index. The index records the min/max values for each block, for a group of blocks and for the entire column within the data shard. |
6868
| **Dynamic** | The ingestion process enumerates all "atomic" elements within the dynamic value, such as property names, values, and array elements, and forwards them to the index builder. Dynamic fields have the same inverted term index as string fields. |
6969

7070
These efficient indexing capabilities enables Data Explore to make the data available in near-real-time for high-performance and high-concurrency queries. The system automatically optimizes data shards to further boost performance.

0 commit comments

Comments
 (0)