You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timestamp field can now be defined at any field mapping level (#3537)
* Fix#3531 - Timestamp field can now be defined at any field mapping level.
* Update index config doc.
* Apply suggestions from code review
Co-authored-by: Adrien Guillo <[email protected]>
* Add new tests to cover edges cases and building from a yaml doc mapper.
---------
Co-authored-by: Adrien Guillo <[email protected]>
Copy file name to clipboardExpand all lines: docs/configuration/index-config.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,15 +88,17 @@ The doc mapping defines how a document and the fields it contains are stored and
88
88
| `field_mappings` | Collection of field mapping, each having its own data type (text, binary, datetime, bool, i64, u64, f64). | `[]` |
89
89
| `mode` | Defines how quickwit should handle document fields that are not present in the `field_mappings`. In particular, the "dynamic" mode makes it possible to use quickwit in a schemaless manner. (See [mode](#mode)) | `lenient`
90
90
| `dynamic_mapping` | This parameter is only allowed when `mode` is set to `dynamic`. It then defines whether dynamically mapped fields should be indexed, stored, etc. | (See [mode](#mode))
91
-
| `tag_fields` | Collection of fields already defined in `field_mappings` whose values will be stored as part of the `tags` metadata. [Learn more about tags](../overview/concepts/querying.md#tag-pruning). | `[]` |
91
+
| `tag_fields` | Collection of fields* already defined in `field_mappings` whose values will be stored as part of the `tags` metadata. [Learn more about tags](../overview/concepts/querying.md#tag-pruning). | `[]` |
92
92
| `store_source` | Whether or not the original JSON document is stored or not in the index. | `false` |
93
-
| `timestamp_field` | Timestamp field used for sharding documents in splits. The field has to be of type `datetime`. [Learn more about time sharding](./../overview/architecture.md). | `None` |
93
+
| `timestamp_field` | Timestamp field* used for sharding documents in splits. The field has to be of type `datetime`. [Learn more about time sharding](./../overview/architecture.md). | `None` |
94
94
`partition_key`| If set, quickwit will route documents into different splits depending on the field name declared as the `partition_key`. | `null` |
95
95
| `max_num_partitions` | Limits the number of splits created through partitioning. (See [Partitioning](../overview/concepts/querying.md#partitioning)) | `200` |
96
96
97
+
*: tags fields and timestamp field are expressed as a path from the root of the JSON object to the given field. If a field name contains a `.` character, it needs to be escaped with a `\` character.
98
+
97
99
### Field types
98
100
99
-
Each field has a type that indicates the kind of data it contains, such as integer on 64 bits or text.
101
+
Each field[^1] has a type that indicates the kind of data it contains, such as integer on 64 bits or text.
100
102
Quickwit supports the following raw types [`text`](#text-type), [`i64`](#numeric-types-i64-u64-and-f64-type), [`u64`](#numeric-types-i64-u64-and-f64-type), [`f64`](#numeric-types-i64-u64-and-f64-type), [`datetime`](#datetime-type), [`bool`](#bool-type), [`ip`](#ip-type), and [`bytes`](#bytes-type), and also supports composite types such as array and object. Behind the scenes, Quickwit is using tantivy field types, don't hesitate to look at [tantivy documentation](https://github.com/tantivy-search/tantivy) if you want to go into the details.
0 commit comments