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
Copy file name to clipboardExpand all lines: docs/dev/intro-v3-engine.md
+4-17Lines changed: 4 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# PPL Engine V3 (for 3.0.0-beta)
1
+
# PPL Engine V3 (for 3.0.0)
2
2
3
3
---
4
4
## 1. Motivations
@@ -24,7 +24,7 @@ Find more details in [V3 Architecture](./intro-v3-architecture.md).
24
24
---
25
25
## 2. What's New
26
26
27
-
In the initial release of the V3 engine (3.0.0-beta), the main new features focus on enhancing the PPL language while maintaining maximum compatibility with V2 behavior.
27
+
In the initial release of the V3 engine (3.0.0), the main new features focus on enhancing the PPL language while maintaining maximum compatibility with V2 behavior.
28
28
29
29
***[Join](../user/ppl/cmd/join.rst) Command**
30
30
***[Lookup](../user/ppl/cmd/lookup.rst) Command**
@@ -35,7 +35,7 @@ In the initial release of the V3 engine (3.0.0-beta), the main new features focu
35
35
36
36
### 3.1 Breaking Changes
37
37
38
-
Because of implementation changed internally, following behaviors are changed from 3.0.0-beta. (Behaviors in V3 is correct)
38
+
Because of implementation changed internally, following behaviors are changed from 3.0.0. (Behaviors in V3 is correct)
@@ -51,7 +51,7 @@ Because of implementation changed internally, following behaviors are changed fr
51
51
52
52
### 3.2 Fallback Mechanism
53
53
54
-
As v3 engine is experimental in 3.0.0-beta, not all PPL commands could work under this new engine. Those unsupported queries will be forwarded to V2 engine by fallback mechanism. To avoid impact on your side, normally you won't see any difference in a query response. If you want to check if and why your query falls back to be handled by V2 engine, please check OpenSearch log for "Fallback to V2 query engine since ...".
54
+
As v3 engine is experimental in 3.0.0, not all PPL commands could work under this new engine. Those unsupported queries will be forwarded to V2 engine by fallback mechanism. To avoid impact on your side, normally you won't see any difference in a query response. If you want to check if and why your query falls back to be handled by V2 engine, please check OpenSearch log for "Fallback to V2 query engine since ...".
55
55
56
56
### 3.3 Limitations
57
57
@@ -66,24 +66,12 @@ For the following functionalities in V3 engine, the query will be forwarded to t
66
66
67
67
#### Unsupported functionalities
68
68
- All SQL queries
69
-
-`trendline`
70
-
-`show datasource`
71
-
-`explain`
72
-
-`describe`
73
-
-`top` and `rare`
74
-
-`fillnull`
75
-
-`patterns`
76
69
-`dedup` with `consecutive=true`
77
70
- Search relevant commands
78
71
- AD
79
72
- ML
80
73
- Kmeans
81
74
- Commands with `fetch_size` parameter
82
-
- query with metadata fields, `_id`, `_doc`, etc.
83
-
- Json relevant functions
84
-
- cast to json
85
-
- json
86
-
- json_valid
87
75
- Search relevant functions
88
76
- match
89
77
- match_phrase
@@ -105,6 +93,5 @@ If you're interested in the new query engine, please find more details in [V3 Ar
105
93
The following items are on our roadmap with high priority:
106
94
- Resolve the [V3 limitation](#33-limitations).
107
95
- Advancing pushdown optimization and benchmarking
108
-
- Backport to 2.19.x
109
96
- Unified the PPL syntax between [PPL-on-OpenSearch](https://github.com/opensearch-project/sql/blob/main/ppl/src/main/antlr/OpenSearchPPLParser.g4) and [PPL-on-Spark](https://github.com/opensearch-project/opensearch-spark/blob/main/ppl-spark-integration/src/main/antlr4/OpenSearchPPLParser.g4)
0 commit comments