From 101b8fead26e52b350ec1fdcf1d651480077da9c Mon Sep 17 00:00:00 2001 From: Stephen Lawrence Date: Tue, 6 Aug 2024 18:49:47 +0100 Subject: [PATCH] example doc: further updates before spell checking Signed-off-by: Stephen Lawrence --- examples/vehicle-speed-downsample-iotdb/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/vehicle-speed-downsample-iotdb/README.md b/examples/vehicle-speed-downsample-iotdb/README.md index 4c469e4..cde3229 100644 --- a/examples/vehicle-speed-downsample-iotdb/README.md +++ b/examples/vehicle-speed-downsample-iotdb/README.md @@ -154,7 +154,7 @@ In this How-To we will use the IoTDB CLI client to send SQL commands on its comm ~~~ ### Down-sample the data -In the previous steps we imported the dataset `vehicle_speed_rl_dataset.csv` into the timeseries `` root.test2.vin123test.`Vehicle.Speed` `` in IoTDB. Now we will down-sample the timeseries using an SQL query and the `Sample` function. The queries will be executed in the IoTDB CLI client. +In the previous steps we imported the dataset `vehicle_speed_rl_dataset.csv` into the timeseries `` root.test2.vin123test.`Vehicle.Speed` `` in IoTDB. Now we will down-sample the timeseries using an SQL query that uses the `Sample` function. The queries will be executed in the IoTDB CLI client. SQL queries can contain a wide range of optional clauses to determine the data that is processed. For example, you can limit the query to a specific time range to isolate a specific journey for the [example scenario](#example-scenario-journey-analysis) at the start of this document.