Currently, cocoindex.init() is needed for most operations. cocoindex.init() requires a Postgres database setting (for cocoindex internal storage).
For some cases, a database as internal storage is not needed:
- Users don't want to build/update index. They only need to query, but needs to do this using CocoIndex's transform flow.
- In tests. For example, sometimes we only want to involve transform flows in tests (it involves both Rust and Python, so can already cover a broad range of cocoindex logic even without bringing up database!).
We should make the database setting optional, and complain on operations that requires cocoindex internal db.
❤️ Contributors, please refer to 📙Contributing Guide.
Unless the PR can be sent immediately (e.g. just a few lines of code), we recommend you to leave a comment on the issue like I'm working on it or Can I work on this issue? to avoid duplicating work. Our Discord server is always open and friendly.