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

[BUG] Interactive: Primary key id should be int64 or string #3693

Closed
lidongze0629 opened this issue Apr 8, 2024 · 0 comments · Fixed by #3761
Closed

[BUG] Interactive: Primary key id should be int64 or string #3693

lidongze0629 opened this issue Apr 8, 2024 · 0 comments · Fixed by #3761
Assignees

Comments

@lidongze0629
Copy link
Collaborator

Describe the bug

Create a graph with DT_DOUBLE as primary key type
Status code return 200(successfully created graph) but with Primary key id should be int64 or string error message during creating graph process.

截屏2024-04-08 10 49 32

zhanglei1949 added a commit that referenced this issue Apr 16, 2024
…ovide file-based implementation (#3696)

Interactive need to maintain the metadata of Graph and Stored
Procedures, which are currently stored as files on disk separately.

We introduce MetaDataStore to govern all metadata storage, querying and
update, and provided a basic implementation based on local file storage.

Support non-blocking graph data loading #3697 
Fix bug #3693
zhanglei1949 added a commit that referenced this issue May 17, 2024
- Create a graph with no edge types.
- Return the detail message when error happens. e.g. creating graph with
vertex have `DT_DOUBLE` primary keys(currently not supported)
- Support open and running query on an empty graph.
- Other issues.

Fix #3707 
Fix #3693
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants