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
As we discussed before in the Nebula community, in the openCypher standard, MATCH (m)-[]->(n), (n)-[]->(l) and MATCH (m)-[]->(n)-[]->(l) are equivalent and not equivalent to MATCH (m)-[]->(n) MATCH (n)-[]->(l). However, in the Nebula implementation, since the execution plan is generated according to a single comma-separated path, the Traverse operator determines and eliminates the duplication of edges only for the single comma-separated path, so that MATCH (m)-[]->(n), (n)-[]->(l) and MATCH (m)-[]->(n) MATCH (n)-[]->(l) are equivalent in Nebula, but not equivalent to MATCH (m)-[]->(n)-[]->(l).
The text was updated successfully, but these errors were encountered:
As we discussed before in the Nebula community, in the openCypher standard, MATCH (m)-[]->(n), (n)-[]->(l) and MATCH (m)-[]->(n)-[]->(l) are equivalent and not equivalent to MATCH (m)-[]->(n) MATCH (n)-[]->(l). However, in the Nebula implementation, since the execution plan is generated according to a single comma-separated path, the Traverse operator determines and eliminates the duplication of edges only for the single comma-separated path, so that MATCH (m)-[]->(n), (n)-[]->(l) and MATCH (m)-[]->(n) MATCH (n)-[]->(l) are equivalent in Nebula, but not equivalent to MATCH (m)-[]->(n)-[]->(l).
The text was updated successfully, but these errors were encountered: