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
Processing of an Initial Query Request has few extra steps comparing versus processing a regular Query Request:
452
452
1. Query validation with `CanPaginateVisitor`. This is required to validate whether incoming query can be paged. This also activate legacy engine fallback mechanism.
453
-
2. Creating a paged index scan with `CreatePagingTableScanBuilder``Optimizer` rule. A Regular Query Request triggers `CreateTableScanBuilder` rule instead.
454
-
3.`Serialization` is performed by `PlanSerializer` - it converts Physical Plan Tree into a cursor, which could be used query a next page.
453
+
2.`Serialization` is performed by `PlanSerializer` - it converts Physical Plan Tree into a cursor, which could be used query a next page.
455
454
456
455
```mermaid
457
456
sequenceDiagram
@@ -496,30 +495,28 @@ Subsequent pages are processed by a new workflow. The key point there:
496
495
497
496
```mermaid
498
497
sequenceDiagram
499
-
participant SQLService
500
498
participant QueryPlanFactory
501
499
participant QueryService
502
-
participant OpenSearchExecutionEngine
500
+
participant Analyzer
501
+
participant Planner
503
502
participant DefaultImplementor
504
503
participant PlanSerializer
504
+
participant OpenSearchExecutionEngine
505
505
506
-
SQLService ->>+ QueryPlanFactory : execute
507
-
QueryPlanFactory ->>+ QueryService : execute
508
-
rect rgb(91, 123, 155)
509
-
note over QueryService, PlanSerializer : Deserialization
510
-
QueryService ->>+ PlanSerializer: convertToPlan
511
-
PlanSerializer -->>- QueryService: Physical plan tree
512
-
end
513
-
Note over QueryService : Planner, Optimizer and Implementor<br />are skipped
0 commit comments