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

NebulaDaoBasic‘s Schema support-show metas #237

Open
wey-gu opened this issue Sep 29, 2023 · 2 comments
Open

NebulaDaoBasic‘s Schema support-show metas #237

wey-gu opened this issue Sep 29, 2023 · 2 comments

Comments

@wey-gu
Copy link
Member

wey-gu commented Sep 29, 2023

Hi @amritagg
I'm glad you're interested in these features.

We need to add methods to NebulaDaoBasic that allow developers to quickly access data without having to write ngql
Just like its other interfaces.https://github.com/nebula-contrib/ngbatis/blob/master/src/main/java/org/nebula/contrib/ngbatis/proxy/NebulaDaoBasic.java

The idea is to extract the more commonly used scripts, as the name of the task item means.

For example, show metas, developers can quickly get schema information by calling the interface, tag, edgeType, etc.

cc: @wey-gu

Originally posted by @CorvusYe in #234 (comment)

@wey-gu wey-gu mentioned this issue Sep 29, 2023
12 tasks
@wey-gu
Copy link
Member Author

wey-gu commented Sep 29, 2023

I think underneath it's calling

SHOW TAGS
SHOW EDGES

And then to call

SHOW TAG <FOO_TAG>;
SHOW TAG <BAR_TAG>;
SHOW EDGE <A_EDGE_TYPE>;
SHOW EDGE <B_EDGE_TYPE>;

And put schema info into one object?

If that's the case, I implemented similar functions here as a reference:

https://github.com/jerryjliu/llama_index/blob/f8c07e8eeb52cc774d9a6334effcbe4c132daef5/llama_index/graph_stores/nebulagraph.py#L596

@CorvusYe

@shbone
Copy link
Contributor

shbone commented Oct 14, 2023

That sounds useful! I will have a try to achieve the show the meta-structure of the graph
maybe the output of it will be a map structure like
space:test
tag :[tagA,tagB,...]
edge: [ edgeA,edgeB,...]
tagIndex:[tagIndexA,tagIndexB,...]
edgeIndex:[edgeIndexA,edgeIndexB]
...
reference to this function
https://github.com/run-llama/llama_index/blob/f8c07e8eeb52cc774d9a6334effcbe4c132daef5/llama_index/graph_stores/nebulagraph.py#L596-L660

I think underneath it's calling

SHOW TAGS
SHOW EDGES

And then to call

SHOW TAG <FOO_TAG>;
SHOW TAG <BAR_TAG>;
SHOW EDGE <A_EDGE_TYPE>;
SHOW EDGE <B_EDGE_TYPE>;

And put schema info into one object?

If that's the case, I implemented similar functions here as a reference:

https://github.com/jerryjliu/llama_index/blob/f8c07e8eeb52cc774d9a6334effcbe4c132daef5/llama_index/graph_stores/nebulagraph.py#L596

@CorvusYe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants