How are node and relationship schemas created/updated when exporting to Kuzu

[petrarca]

Following the example(s), I was not able to successfully export a knowledge graph to Kuzu.
Seems the problem is that schemas need to be pre-defined for nodes and relations:

 Caused by:
        Failed to run cypher: {"error":"Binder exception: Table Entity does not exist."}
[2025-08-04T16:37:31Z ERROR cocoindex_engine::execution::source_indexer] Error in processing row from source `documents` with key: "docs/getting_started/installation.md"

How is the usage here intended?

[georgeh0]

CocoIndex automatically creates tables during "setup", i.e. when you run cocoindex setup or cocoindex update --setup. It will show the tables that it'll create and ask you to confirm, like this:

If you're not using the CLI, the setup() API will do it.

If you see this error, it's probably one of the following reasons:

1. Between you run cocoindex setup and cocoindex update, you switched the Kuzu database, e.g. you started a new Kuzu container (using the same port) but you didn't keep the underlying db files or it points to a different location.

   If this is the case, you can run cocoindex drop -f main.py to reset your existing states first. After this, cocoindex will know the backend tables are gone, so it will create it in the next cocoindex setup or cocoindex update --setup run.

2. You set setup_by_user = True in the export() (see related docs for its purpose). CocoIndex won't create the tables for you under this scenario.

Please let us know if that's the case. We can help to dig further if it's other situations. Thanks!

[badmonster0]

@petrarca thank you so much for the amazing questions and feedbacks, we love it!
I'm one of the founders at CocoIndex, wonder if you'd be open to a casual chat with us - [email protected]? If you are open to it, would love to learn more about your use case and feedback for coco and how do we support your better, thanks!