Skip to content

Commit e30c295

Browse files
committed
remove v1 index properties
1 parent 123180c commit e30c295

File tree

1 file changed

+0
-16
lines changed

1 file changed

+0
-16
lines changed

articles/cosmos-db/index-policy.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -87,22 +87,6 @@ Any indexing policy has to include the root path `/*` as either an included or a
8787

8888
- If the indexing mode is set to **consistent**, the system properties `id` and `_ts` are automatically indexed.
8989

90-
When including and excluding paths, you may encounter the following attributes:
91-
92-
- `kind` can be either `range` or `hash`. Hash index support is limited to equality filters. Range index functionality provides all of the functionality of hash indexes as well as efficient sorting, range filters, system functions. We always recommend using a range index.
93-
94-
- `precision` is a number defined at the index level for included paths. A value of `-1` indicates maximum precision. We recommend always setting this value to `-1`.
95-
96-
- `dataType` can be either `String` or `Number`. This indicates the types of JSON properties that will be indexed.
97-
98-
It's no longer necessary to set these properties. When not specified, these properties will have the following default values:
99-
100-
| **Property Name** | **Default Value** |
101-
| ----------------------- | -------------------------------- |
102-
| `kind` | `range` |
103-
| `precision` | `-1` |
104-
| `dataType` | `String` and `Number` |
105-
10690
See [this section](how-to-manage-indexing-policy.md#indexing-policy-examples) for indexing policy examples for including and excluding paths.
10791

10892
## Include/exclude precedence

0 commit comments

Comments
 (0)