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

feat: ngql reader to support arbitrary query result parsing #132

Closed
wey-gu opened this issue Nov 21, 2023 · 0 comments · Fixed by #133
Closed

feat: ngql reader to support arbitrary query result parsing #132

wey-gu opened this issue Nov 21, 2023 · 0 comments · Fixed by #133
Labels
help wanted Community: does anyone want to work on it? type/feature req Type: feature request

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Nov 21, 2023

Now only MATCH ()-[e:xx]->() return e LIMIT 10000is supported, ideally we could parse all edges of arbitrary results to enable complex MATCH/FIND PATH/GET SUBGRAPH to be leveraged, just add a whitelist of parsed edge schema.

@wey-gu wey-gu added type/feature req Type: feature request help wanted Community: does anyone want to work on it? labels Nov 21, 2023
wey-gu added a commit to wey-gu/nebula-spark-connector that referenced this issue Nov 21, 2023
Nicole00 pushed a commit that referenced this issue Dec 21, 2023
* feat: support path in nGQL, not raise exception for other types

close #132

* fix typing and error handling as commented

* handle List Value typing

* wording of the exception and logging

* fix typing, added test for ngql

* test: add GET SUBGRAPH and FIND PATH

* fix ngql example and test cases

* fix typo in withConnectionRetry

* add back withConnectionRetry in ngql tests

* fix missing operateType

* fix null pointer

* test: add with prop for prop reading

* docs: update examples for with prop clause
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Community: does anyone want to work on it? type/feature req Type: feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant