Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The match statement is semantically incompatible with the openCypher standard for Trail. #5394

Open
Salieri-004 opened this issue Mar 9, 2023 · 0 comments
Labels
type/feature req Type: feature request

Comments

@Salieri-004
Copy link
Contributor

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
None yet
Development

No branches or pull requests

1 participant