From e1eb0459289ad4a78ee702cc4f6e75622e2e2dc7 Mon Sep 17 00:00:00 2001
From: Abby <78209557+abby-cyber@users.noreply.github.com>
Date: Tue, 21 Mar 2023 16:58:27 +0800
Subject: [PATCH] disable-edgelist-join

---
 .../3.ngql-guide/7.general-query-statements/2.match.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md b/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
index 5ee42e3e779..0c65f662c1c 100644
--- a/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
+++ b/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
@@ -600,6 +600,16 @@ nebula> MATCH p=(v:player{name:"Tim Duncan"})-[e:follow*0..3]->(v2:player) \
 +-----------------------------------------------------------+-----------+
 ```
 
+!!! note
+
+    When using the variable `e` to match fixed-length or variable-length paths in a pattern, such as `-[e:follow*0..3]->`, it is not supported to reference `e` in other patterns. For example, the following statement is not supported.
+
+    ```ngql
+    nebula> MATCH (v:player)-[e:like*1..3]->(n) \
+            WHERE (n)-[e*1..4]->(:player) \
+            RETURN v;
+    ```
+
 ### Match variable-length paths with multiple edge types
 
 You can specify multiple edge types in a fixed-length or variable-length pattern. In this case, `hop`, `minHop`, and `maxHop` take effect on all edge types.