Hey, friends! Ever heard of traditional Chinese medicine? Think of it as nature's pharmacy—using plants, herbs, and even insects to heal. Sounds a bit like something out of a witch’s spellbook!🪄🔮 Check out this awesome article on building a knowledge graph for treating rhinitis using traditional Chinese medicine with NebulaGraph. It’s a fascinating blend of ancient wisdom and cutting-edge tech. Let’s dig in!⬇️ https://www.nebula-graph.io/posts/Rhinitis%20Knowledge%20Graph

"""""""çX!!!1‘’‘’‘’‘’‘’‘’‘’‘’‘’‘’‘。/˘

Hi, are there any plans to support NebulaGraph Cloud for GCP? We are considering NebulaGraph for an upcoming project and this would be an important consideration for us. Thank you

i am trying to use the nebula-importer utility and running into issues where i get the error: unsupported client version:

image.png

nebula version is 3.8.0

Any plans on improving the various client SDKs?

Dgraph is much much better in this regard. The DX is just higher level.

Happy Chinese new year BTW!

Hey NebulaGraph Community! I have decided to make public my golang-SDK which facilitates client connection pooling(via robust library rather than writing it from scratch, context cancellation much easier. And would like to bring my repository to nebula’s community driven repositories to make it accessible by nebula users. Wdyt? Link to repo: https://github.com/egasimov/nebula-go-sdk P:S Happy Chinese new year!

Hello, I'm trying to run a GQL script on the NebulaGraph Studio Console to create a Graph model from scratch, but I can't seem to execute the GQL commands in the console prompt. The script was initially created in Neo4j Cypher, and I am trying to recreate the Graph in Nebula. Do you know how I can execute GQL commands in the Console?

Hello. i after loading the nodes in a graph using the Nebula Importer, i issued a simple query where i just want to get count of the nodes, and i see various errors: 1. [ERROR (-1005)]: Storage Error: RPC failure, probably timeout. ~ for this i commented out the property : --storage_client_timeout_ms=60000 , then i got the error " Used memory hits the high watermark(0.800000) of total system memory" i changed the threshold from 0.8 to 0.9, then again i get the same RPC Failure again .. any guidance on this?

Hello dear friend I have a few questions Although my questions are repetitive, I don't know what to do due to the difference in nebula graph versions Please advise It is very important to me Compaction version in use Operating system: latest version of ubuntu 1: The writing speed is very slow How can I increase it to the highest speed? I am using bath insert but it takes a long time to respond Over time, as data is added, the writing speed becomes very slow and the RAM fills up quickly 2: Does compaction run automatically after insert? If it can -> how can I disable it so that it doesn't run automatically? Please advise Thank you very much

Friends When I start bath insert, the RAM consumption increases over time until it even exceeds 0.8 and occupies all the RAM memory and finally gives the error {Unknown error -3521!} How do I solve the problem?

This article explores how graph databases are becoming crucial for the development of AI and LLMs. It discusses the limitations of traditional databases and how graph technology can help overcome these challenges. If you're interested in the intersection of AI and graph databases, this is definitely worth a read!👀https://www.nebula-graph.io/posts/nebulagraph_essential_for_the_next_generation_of_ai_and_llms

Hi I have an issue After I deleted the CreatedAt field with the data type is String Then I could not add the CreatedAt field with the data type of int64. Nebula notification: Schema Exisited Before! Although when I use the describe command. I no longer see createdAt field

Are you guys doing anything in direction of RDF graphs and joining them with LPG?

Hi all. I've been having a lot of trouble uploading some data from a .conllu file into a nebula graph space managed by the docker extension. My project is a python project. After failing to properly import the data based on my schema and model I tried using the AI importer in nebula studio on my dataset (a .conllu file) From there I downloaded the schema dll. But I'm still struggling to figure out how to import the data into nebula graph while having it fit my model. Any help or guidance would be greatly appreciated. I will want to be importing big datasets so need some batching capabilities too. Should I be using nebula-carina to simplify my life? Is that ORM layer still in active development? And would it slow down my graph operations (this code is part of a GNN).

Are there any plans/timeline to bring ISO-GQL to Nebula's Community Edition?

Hi. Sorry for the nube question. Is Nebula Graph a Labeled Property type of graph DB or its RDF? Or maybe, it can do both? This was a bit ambiguous to me: “NebulaGraph: Users can create and modify their data models on-the-fly, without the need for any pre-defined schemas or constraints.This allows users to model their data in a way that best fits their specific use case, without being constrained by pre-existing schemas. It also supports property graphs.” https://www.nebula-graph.io/posts/best-graph-database-for-enterprise

Hi. I'm fairly new to the graph world. so far have only relied on a sigmajs based debugging visualization driven by realtime events ( distributed networking integration / debugging context ). I'm exploring the possibilities regarding persisting data too. looked at kuzu ( Fully awar it has a totally different scope that this project ) and recently found nebula. Was wondering if there are any "streaming / live query" concepts in a database like nebula? I'm basically trying to find a good match for an erlang based system with many "graph like" concepts like supervision trees, message passing, ... and the distributed and opensource characteristics of nebula is what catched my attention. not so sure about the query language though. is nebula the only product using it? or is nGQL based on some "underlying" standard?

is there online documentation on how to setup a RAG frontend to nebula like whats shown in the LLM graphDB blogpost using self hosted nebula?

is there any way to assign a "list" of strings as a property in a tag definition? Im trying to write automation to transform a list of "events" in the form of a list of python dictionaries into a schema by leveraging the type relationships, but ive hit an edge case. If a dict contains a list of values (lets say strings), I can't generate a unique property name for each value and add each list item as a property of the parent object because the positioning of the value would changes its property definition and result in an infinitely complex schema but, I cant just generate a property name based on the parent field either because then id have multiple properties with the same name

hm, i guess i could make single property tags and then just link the tags to the parent with weighted edges... that would make for an exceptionally complicated graph tho...

I also just found this solution https://stackoverflow.com/questions/75014401/how-to-add-list-type-properties-to-vertices-in-the-nebulagraph-database but that seems.... not ideal

ended up just going with the edge to self option <_<

im running into an issue trying to use

upsert_nodes

File "/Users/carl/external/miniconda3/envs/dev/lib/python3.10/site-packages/llama_index/graph_stores/nebula/nebula_property_graph.py", line 272, in upsert_nodes
    self.structured_query(
  File "/Users/carl/external/miniconda3/envs/dev/lib/python3.10/site-packages/llama_index/graph_stores/nebula/nebula_property_graph.py", line 550, in structured_query
    raise Exception(
Exception: ('NebulaGraph query failed:', "SemanticError: No schema found for `Entity__'", 'Statement:', 'INSERT VERTEX `Entity__` (`name`) VALUES "1":($entity_0),"0":($entity_1),"1":($entity_2),"0":($entity_3),"1":($entity_4),"0":($entity_5),"1":($entity_6),"0":($entity_7),"1":($entity_8),"0":($entity_9),"1":($entity_10),"0":($entity_11),"1":($entity_12),"0":($entity_13),"1":($entity_14),"0":($entity_15),"1":($entity_16),"0":($entity_17),"1":($entity_18),"0":($entity_19),"1":($entity_20),"0":($entity_21),"1":($entity_22),"0":($entity_23),"1":($entity_24),"0":($entity_25),"1":($entity_26),"0":($entity_27),"1":($entity
.............. *clipped for brevity* ..............

my insert statement looks like this

graph_store.upsert_nodes(nodes)

and my graph store looks like this

graph_store = NebulaPropertyGraphStore(space=space_name, props_schema=", ".join(props_schema))

i am manually adding my schema tags and edge types in a separate codeblock. That seems to not matter as when i look at the source, the issue appears to be coming from some forced default nebula syntax entry within llama_index Is it required that I copy the syntax used and manually add it to my schema? i'm confused on the correct way to work around this error

I see now that many implementations are using the default

DDL

s and as such utilize the template at the top of that same source page, so ill have to implement the parts of it i need i guess? Im not sure what the "right" way to do this is

im still stuck, ive cleaned up my code a LOT and im inspecting the schema string before it goes into the graph store and it appears to have the correct values but still fails (now via the identical error in the git issue)

The error is

Exception: ('NebulaGraph query failed:', "SemanticError: Unknown column `src_process_image_path' in schema", 'Statement:', 'INSERT VERTEX Props__......

and the props_schema string starts with

`src_process_image_path` STRING....