update explain analyze from 2091 (#1096)

Author: leto-bbq

src/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md

@@ -151,6 +151,17 @@ A `FragmentInstance` is a wrapper for a query shard in IoTDB. Each query shard o
 - Ready Queued Time: Total time the shard's tasks spent in the ready queue (tasks are not blocked but lack query execution thread resources).
 - Blocked Queued Time: Total time the shard's tasks spent in the blocked queue (tasks are blocked due to resources like memory or upstream data not being sent).
 
+Since V2.0.9, the following information will be added to `FragmentInstance`:
+
+- `OutputPlanNodeId`: Indicates the downstream node that receives data corresponding to the sink node. Only present in sink nodes.
+- `sizeInBytes`: Represents the size in bytes of TsBlocks received in exchange nodes (only data size is counted). Only present in exchange nodes.
+- Data filtering‑related fields for `tableScan` nodes. Valid only when filter pushdown is applied to tableScan, and only present in tableScan nodes:
+    - `TimeSeriesIndexFilteredRows`: Number of rows filtered out by TimeseriesMetadata
+    - `ChunkIndexFilteredRows`: Number of rows filtered out by ChunkMetadata
+    - `PageIndexFilteredRows`: Number of rows filtered out by PageHeader internal filtering
+    - `RowScanFilteredRows`: Number of rows filtered out during per-row data inspection. Only displayed when `verbose` is enabled.
+
+
 #### BloomFilter-Related Metrics
 
 Bloom filters help determine if a sequence exists in a TsFile. They are stored at the end of each TsFile.

src/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md

@@ -151,6 +151,17 @@ A `FragmentInstance` is a wrapper for a query shard in IoTDB. Each query shard o
 - Ready Queued Time: Total time the shard's tasks spent in the ready queue (tasks are not blocked but lack query execution thread resources).
 - Blocked Queued Time: Total time the shard's tasks spent in the blocked queue (tasks are blocked due to resources like memory or upstream data not being sent).
 
+Since V2.0.9, the following information will be added to `FragmentInstance`:
+
+- `OutputPlanNodeId`: Indicates the downstream node that receives data corresponding to the sink node. Only present in sink nodes.
+- `sizeInBytes`: Represents the size in bytes of TsBlocks received in exchange nodes (only data size is counted). Only present in exchange nodes.
+- Data filtering‑related fields for `tableScan` nodes. Valid only when filter pushdown is applied to tableScan, and only present in tableScan nodes:
+    - `TimeSeriesIndexFilteredRows`: Number of rows filtered out by TimeseriesMetadata
+    - `ChunkIndexFilteredRows`: Number of rows filtered out by ChunkMetadata
+    - `PageIndexFilteredRows`: Number of rows filtered out by PageHeader internal filtering
+    - `RowScanFilteredRows`: Number of rows filtered out during per-row data inspection. Only displayed when `verbose` is enabled.
+
+
 #### BloomFilter-Related Metrics
 
 Bloom filters help determine if a sequence exists in a TsFile. They are stored at the end of each TsFile.

src/zh/UserGuide/Master/Table/User-Manual/Query-Performance-Analysis.md

@@ -156,7 +156,15 @@ Explain Analyze 是 IOTDB 查询引擎自带的性能分析 SQL，与 Explain 
     - loadChunkFromCacheCount: 命中ChunkCache的次数，注意这里对于对齐设备来讲，每个分量（包括time列，都会去单独请求Cache，所以对于对齐设备来讲，（loadChunkFromCacheCount + loadChunkFromDiskCount）= tsfile number * subSensor number(包括time列）* avg chunk number in each tsfile
     - loadChunkFromDiskCount: 从磁盘中读取Chunk的次数，一次只会读取一个分量，并缓存在ChunkCache中
     - loadChunkActualIOSize: 从磁盘中读取Chunk时耗费的磁盘IO（单位为bytes）
-
+    
+    自V2.0.9起，在 FragmentInstance 中，将增加如下信息：
+  - OutputPlanNodeId：表示sink节点对应的下游接收数据的节点，仅在sink节点中出现
+  - sizeInBytes：表示exchange节点中接收到的TsBlock的字节（仅计算数据占用大小），仅在exchange节点中出现
+  - tableScan节点过滤数据相关字段，仅在filter下推到tableScan中才有效，且仅在tableScan节点中出现：
+    - TimeSeriesIndexFilteredRows ： 通过序列元数据（TimeseriesMetadata）过滤掉的数据行数
+    - ChunkIndexFilteredRows： 通过列块元数据（ChunkMetadata）过滤掉的数据行数
+    - PageIndexFilteredRows：通过页头内部（PageHeader）过滤掉的数据行数
+    - RowScanFilteredRows：一行行检查数据时候被过滤掉的行数（仅在带有verbose时才会展现）
 
 ##### 特别说明
 

src/zh/UserGuide/latest-Table/User-Manual/Query-Performance-Analysis.md

@@ -156,6 +156,15 @@ Explain Analyze 是 IOTDB 查询引擎自带的性能分析 SQL，与 Explain 
     - loadChunkFromCacheCount: 命中ChunkCache的次数，注意这里对于对齐设备来讲，每个分量（包括time列，都会去单独请求Cache，所以对于对齐设备来讲，（loadChunkFromCacheCount + loadChunkFromDiskCount）= tsfile number * subSensor number(包括time列）* avg chunk number in each tsfile
     - loadChunkFromDiskCount: 从磁盘中读取Chunk的次数，一次只会读取一个分量，并缓存在ChunkCache中
     - loadChunkActualIOSize: 从磁盘中读取Chunk时耗费的磁盘IO（单位为bytes）
+      
+    自V2.0.9起，在 FragmentInstance 中，将增加如下信息：
+  - OutputPlanNodeId：表示sink节点对应的下游接收数据的节点，仅在sink节点中出现
+  - sizeInBytes：表示exchange节点中接收到的TsBlock的字节（仅计算数据占用大小），仅在exchange节点中出现
+  - tableScan节点过滤数据相关字段，仅在filter下推到tableScan中才有效，且仅在tableScan节点中出现：
+    - TimeSeriesIndexFilteredRows ： 通过序列元数据（TimeseriesMetadata）过滤掉的数据行数
+    - ChunkIndexFilteredRows： 通过列块元数据（ChunkMetadata）过滤掉的数据行数
+    - PageIndexFilteredRows：通过页头内部（PageHeader）过滤掉的数据行数
+    - RowScanFilteredRows：一行行检查数据时候被过滤掉的行数（仅在带有verbose时才会展现）
 
 
 ##### 特别说明