From d5ad000d720be40ce6043f5e0c92c533165701b1 Mon Sep 17 00:00:00 2001 From: Ivan Blinkov Date: Mon, 3 Feb 2020 12:38:01 +0300 Subject: [PATCH] Update index.md --- docs/en/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/index.md b/docs/en/index.md index 0985a15d61b..3a3c2595ec0 100644 --- a/docs/en/index.md +++ b/docs/en/index.md @@ -37,7 +37,7 @@ The data access scenario refers to what queries are made, how often, and in what The higher the load on the system, the more important it is to customize the system set up to match the requirements of the usage scenario, and the more fine grained this customization becomes. There is no system that is equally well-suited to significantly different scenarios. If a system is adaptable to a wide set of scenarios, under a high load, the system will handle all the scenarios equally poorly, or will work well for just one or few of possible scenarios. -## Key Properties of the OLAP scenario +## Key Properties of OLAP Scenario - The vast majority of requests are for read access. - Data is updated in fairly large batches (> 1000 rows), not by single rows; or it is not updated at all.