Remove --max-index-size and --max-task-db-size

dureuill · dureuill · commit b46fa77feb4f · 2022-12-26T17:17:08.000+01:00
diff --git a/text/0034-telemetry-policies.md b/text/0034-telemetry-policies.md
@@ -86,8 +86,6 @@ The collected data is sent to [Segment](https://segment.com/). Segment is a plat
 | `infos.ignore_missing_snapshot`         | `true` if `--ignore_missing_snapshot` is specified to true, otherwise `false` | true | Every Hour |
 | `infos.ignore_snapshot_if_db_exists`    | `true` if `--ignore_snapshot_if_db_exists` is specified to true, otherwise `false` | true | Every Hour |
 | `infos.http_addr`                       | `true` if `--http-addr`/`MEILI_HTTP_ADDR` is specified, otherwise `false` | true| Every Hour |
-| `infos.max_index_size`                  | Value of `--max-index-size`/`MEILI_INDEX_SIZE` in bytes | 336042103 | Every Hour |
-| `infos.max_task_db_size`                | Value of `--max-task-db-size`/`MEILI_MAX_TASK_DB_SIZE` in bytes | 336042103 | Every Hour |
 | `infos.http_payload_size_limit`         | Value of `--http-payload-size-limit`/`MEILI_HTTP_PAYLOAD_SIZE_LIMIT` in bytes | 336042103 | Every Hour |
 | `infos.disable_auto_batching`            | `true` if `--disable-auto-batching`/`MEILI_DISABLE_AUTO_BATCHING` is specified to true, otherwise `false` | `true` | Every Hour |
 | `infos.log_level`                       | Value of `--log-level`/`MEILI_LOG_LEVEL`                | debug             | Every Hour |
@@ -173,7 +171,7 @@ The collected data is sent to [Segment](https://segment.com/). Segment is a plat
 | `filtered_by_before_finished_at`        | `true` if tasks are filtered by the `beforeFinishedAt` query parameter, otherwise `false` | false | `Tasks Seen`, `Tasks Canceled`, `Tasks Deleted` |
 | `filtered_by_after_finished_at`         | `true` if tasks are filtered by the `afterFinishedAt` query parameter, otherwise `false` | false | `Tasks Seen`, `Tasks Canceled`, `Tasks Deleted` |
 | `per_index_uid` | `true` if an uid is used to fetch an index stat resource, otherwise `false` | false | `Stats Seen` |
-| `swap_operation_number`            | The number of swap operation given in `POST /swap-indexes` API call | 2 | `Indexes Swapped` | 
+| `swap_operation_number`            | The number of swap operation given in `POST /swap-indexes` API call | 2 | `Indexes Swapped` |
 | `matching_strategy.most_used_strategy`      | Most used word matching strategy among all search requests in this batch | `last` | `Documents Searched POST`, `Documents Searched GET` |
 | `per_document_id` | `true` if `DELETE /indexes/:indexUid/documents/:documentUid` endpoint was used in this batch, otherwise `false` | false | `Documents Deleted` |
 | `clear_all` | `true` if `DELETE /indexes/:indexUid/documents` endpoint was used in this batch, otherwise `false` | false | `Documents Deleted` |
@@ -214,8 +212,6 @@ This property allows us to gather essential information to better understand on
 | infos.ignore_missing_snapshot | `true` if `--ignore-missing-snapshot` is specified to true, otherwise `false` | `true` |
 | infos.ignore_snapshot_if_db_exists | `true` if `--ignore-snapshot-if-db-exists` is specified to true, otherwise `false` | `true` |
 | infos.http_addr | `true` if `--http-addr`/`MEILI_HTTP_ADDR` is specified, otherwise `false` | `true`|
-| infos.max_index_size | Value of `--max-index-size`/`MEILI_INDEX_SIZE` in bytes | `336042103` |
-| infos.max_task_db_size | Value of `--max-task-db-size`/`MEILI_MAX_TASK_DB_SIZE` in bytes | `336042103` |
 | infos.http_payload_size_limit | Value of `--http-payload-size-limit`/`MEILI_HTTP_PAYLOAD_SIZE_LIMIT` in bytes | `336042103` |
 | infos.disable_auto_batching | `true` if `--disable-auto-batching`/`MEILI_DISABLE_AUTO_BATCHING` is specified to true, otherwise `false` | `true` |
 | infos.log_level | Value of `--log-level`/`MEILI_LOG_LEVEL`  | `debug` |
diff --git a/text/0060-tasks-api.md b/text/0060-tasks-api.md
@@ -534,50 +534,46 @@ HTTP Code: `404 Not Found`
 
 - The `:taskUid` is inferred when the message is generated.
 
-#### 8. `MEILI_MAX_TASK_DB_SIZE` env var and `--max-task-db-size` CLI option
-
-See [0119-instance-options](0119-instance-options.md##3312-max-taskdb-size)
-
-#### 9. Asynchronous Write Operations on Index resource
+#### 8. Asynchronous Write Operations on Index resource
 
 - 💡 Automatic index creation using the `/indexes/:indexToCreate/documents` route generates a `documentAdditionOrUpdate` task that also handles index creation.
 
-#### 10. Paginate `task` resource lists
+#### 9. Paginate `task` resource lists
 
 The API endpoint `GET /tasks` is browsable using a keyset-based pagination.
 
-##### 10.1. Why a Seek/Keyset based pagination?
+##### 9.1. Why a Seek/Keyset based pagination?
 
 Keyset-based pagination is more appropriate when the data can grow or shrink quickly in terms of magnitude.
 
-###### 10.1.1. Pros
+###### 9.1.1. Pros
 
 The performance is better than the not-so-good but old pagination with `offset`/`limit`.
 
 Seek/Keyset pagination keeps the results consistent between each page as the data evolves. It avoids the [Page Drift effect](https://use-the-index-luke.com/sql/partial-results/fetch-next-page), especially when the data is sorted from the most recent to the oldest.
 
 Moreover, the performance is superior to traditional pagination since the computational complexity remains constant to reach the identifier marking the beginning of the new slice to be returned from a hash table.
 
-###### 10.1.2. Cons
+###### 9.1.2. Cons
 
 The main drawback of this type of pagination is that it does not navigate within a finite number of pages. It is also limited to a precise sorting criterion on unique identifiers ordered sequentially.
 
-##### 10.2. Response attributes
+##### 9.2. Response attributes
 
 | field | type | description                          |
 |-------|------|--------------------------------------|
 | limit | integer  | Default `20`. |
 | from | integer | The first task uid returned |
 | next | integer - nullable  | Represents the value to send in `from` to fetch the next slice of the results. The first item for the next slice starts at this exact number. When the returned value is null, it means that all the data have been browsed in the given order. |
 
-##### 10.3. GET query parameters
+##### 9.3. GET query parameters
 
 | field | type | required | description  |
 |-------|------|----------|--------------|
 | limit | integer  | No       | Default `20`. Limit on the number of tasks to be returned. |
 | from | integer  | No       | Limit results to tasks with uids equal to and lower than this uid. |
 
-##### 10.4. Usage examples
+##### 9.4. Usage examples
 
 This part demonstrates keyset paging in action on `/tasks`. The items `uid` remains sorted sequentially and can be used to navigate a list of `tasks` objects.
 
@@ -666,26 +662,26 @@ This part demonstrates keyset paging in action on `/tasks`. The items `uid` rema
 
 - 💡 `next` response parameter is null because there are no more `tasks` to fetch. It means that the response represents the last slice of results for the given resource list.
 
-##### 10.5. Behaviors for `limit` and `from` query parameters
+##### 9.5. Behaviors for `limit` and `from` query parameters
 
-###### 10.5.1. `limit`
+###### 9.5.1. `limit`
 
 - If `limit` is not set, the default value is chosen.
 
-###### 10.5.2. `from`
+###### 9.5.2. `from`
 
 - If `from` is set with an out of bounds task `uid`, the response returns the tasks that are the nearest to the specified uid, the `next` field is set to the next page. It will be equivalent to call the `/tasks` route without any parameter.
 
-###### 10.5.3. Errors
+###### 9.5.3. Errors
 
 - 🔴 Sending a value with a different type than `Integer` for `limit` returns a [bad_request](0061-error-format-and-definitions.md#bad_request) error.
 - 🔴 Sending a value with a different type than `Integer` for `from` returns a [bad_request](0061-error-format-and-definitions.md#bad_request) error.
 
-#### 11. Filtering task resources
+#### 10. Filtering task resources
 
 The tasks API endpoints are filterable by  `uids`, `indexUids`, `types`, `statuses`, `canceledBy`, `beforeEnqueuedAt`, `afterEnqueuedAt`, `beforeStartedAt`, `afterStartedAt`, `beforeFinishedAt`,  `afterFinishedAt` query parameters.
 
-##### 11.1 Query parameters definition
+##### 10.1 Query parameters definition
 
 | parameter | type   | required | description                                                                                                                                                                                                                             |
 |-----------|--------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -701,9 +697,9 @@ The tasks API endpoints are filterable by  `uids`, `indexUids`, `types`, `status
 | beforeFinishedAt | string | No       | Filter tasks based on their finishedAt time. Retrieve tasks finished before the given filter value.  |
 | afterFinishedAt | string | No       | Filter tasks based on their finishedAt time. Retrieve tasks finished after the given filter value.                 |
 
-##### 11.2. Query Parameters Behaviors
+##### 10.2. Query Parameters Behaviors
 
-###### 11.2.1. `uids`
+###### 10.2.1. `uids`
 
  Filter tasks by their related unique identifier. By default, when `uids` query parameter is not set, all the tasks are concerned. It is possible to specify several uid by separating them with the `,` character.
 
@@ -715,7 +711,7 @@ The tasks API endpoints are filterable by  `uids`, `indexUids`, `types`, `status
 
 - 🔴 Sending values with a different type than `Integer` being separated by `,` for the `uid` parameter returns an [`invalid_task_uids_filter`](0061-error-format-and-definitions.md#invalid_task_uids_filter) error.
 
-###### 11.2.2. `indexUids`
+###### 10.2.2. `indexUids`
 
 Filter tasks by their related index. By default, when `indexUids` query parameter is not set, the tasks of all the indexes are concerned. It is possible to specify several indexUids by separating them with the `,` character.
 
@@ -725,7 +721,7 @@ Filter tasks by their related index. By default, when `indexUids` query paramete
 
 `indexUids` is **case-sensitive**.
 
-###### 11.2.3. `statuses`
+###### 10.2.3. `statuses`
 
 Filter tasks by their status. By default, when `statuses` query parameter is not set, all task statuses are concerned. It's possible to specify several statuses by separating them with the `,` character.
 
@@ -737,7 +733,7 @@ Filter tasks by their status. By default, when `statuses` query parameter is not
 
 - 🔴 If the `statuses` parameter value is not consistent with one of the task statuses, an [`invalid_task_statuses_filter`](0061-error-format-and-definitions.md#invalid_task_statuses_filter) error is returned.
 
-###### 11.2.4. `types`
+###### 10.2.4. `types`
 
 Filter tasks by their related type. By default, when `types` query parameter is not set, all task types are concerned. It's possible to specify several types by separating them with the `,` character.
 
@@ -749,7 +745,7 @@ Filter tasks by their related type. By default, when `types` query parameter is
 
 - 🔴 If the `types` parameter value is not consistent with one of the task types, an [`invalid_task_types_filter`](0061-error-format-and-definitions.md#invalid_task_types_filter) error is returned.
 
-###### 11.2.5. `canceledBy`
+###### 10.2.5. `canceledBy`
 
 Filter tasks by the `taskCancelation` uid that canceled them. It's possible to specify several task uids by separating them with the `,` character.
 
@@ -761,15 +757,15 @@ Filter tasks by the `taskCancelation` uid that canceled them. It's possible to s
 
 - 🔴Sending a value with a different type than `Integer` for the `canceledBy` parameter returns an [`invalid_task_canceled_by_filter`](0061-error-format-and-definitions.md#invalid_task_canceled_by_filter) error.
 
-###### 11.2.6. Date Parameters
+###### 10.2.6. Date Parameters
 
 Date filters accepts the RFC 3339 format. The following syntaxes are valid:
 
 - `YYYY-MM-DD`
 - `YYYY-MM-DDTHH:MM:SSZ`
 - `YYYY-MM-DDTHH:MM:SS+01:00`
 
-###### 11.2.6.1. `beforeEnqueuedAt` and `afterEnqueuedAt`
+###### 10.2.6.1. `beforeEnqueuedAt` and `afterEnqueuedAt`
 
 Filter tasks based on their enqueuedAt time. Retrieve tasks enqueued before/after the given filter value.
 
@@ -780,7 +776,7 @@ Filter tasks based on their enqueuedAt time. Retrieve tasks enqueued before/afte
 - 🔴 The date filters are exclusive. It means the given value will not be included.
 - 🔴 Sending an invalid value for the date parameter returns an [`invalid_task_date_filter`](0061-error-format-and-definitions.md#invalid_task_date_filter) error.
 
-###### 11.2.6.2. `beforeStartedAt` and `afterStartedAt`
+###### 10.2.6.2. `beforeStartedAt` and `afterStartedAt`
 
 Filter tasks based on their startedAt time. Retrieve tasks started before/after the given filter value.
 
@@ -791,7 +787,7 @@ Filter tasks based on their startedAt time. Retrieve tasks started before/after
 - 🔴 The date filters are exclusive. It means the given value will not be included.
 - 🔴 Sending an invalid value for the date parameter returns an [`invalid_task_date_filter`](0061-error-format-and-definitions.md#invalid_task_date_filter) error.
 
-###### 11.2.6.3. `beforeFinishedAt` and `afterFinishedAt`
+###### 10.2.6.3. `beforeFinishedAt` and `afterFinishedAt`
 
 Filter tasks based on their finishedAt time. Retrieve tasks finished before/after the given filter value.
 
@@ -803,15 +799,15 @@ Filter tasks based on their finishedAt time. Retrieve tasks finished before/afte
 - 🔴 Sending an invalid value for the date parameter returns an [`invalid_task_date_filter`](0061-error-format-and-definitions.md#invalid_task_date_filter) error.
 
 
-###### 11.2.7. Select multiple values for the same filter
+###### 10.2.7. Select multiple values for the same filter
 
 It is possible to specify multiple values for a filter using the `,` character.
 
 For example, to select the `enqueued` and `processing` tasks of the `movies` and `movie_reviews` indexes, it is possible to express it like this: `/tasks?indexUids=movies,movie_reviews&statuses=enqueued,processing`
 
 ---
 
-##### 11.3. Usages examples
+##### 10.3. Usages examples
 
 This part demonstrates filtering on `/tasks`.
 
@@ -986,7 +982,7 @@ This part demonstrates filtering on `/tasks`.
 
 ---
 
-##### 11.4. Empty `results`
+##### 10.4. Empty `results`
 
 If no results match the filters. A response is returned with an empty `results` array.
 
diff --git a/text/0119-instance-options.md b/text/0119-instance-options.md
