Add ChromaDB service #1
Conversation
TotallyNotChase
force-pushed
the
chase/chromadb
branch
from
ca041a5 to
991f268
Compare
TotallyNotChase
force-pushed
the
chase/chromadb
branch
from
991f268 to
4297d88
Compare
| StringMeta(String), | ||
| NumberMeta(i64), | ||
| NullMeta, | ||
| // TODO (chase): Support floating point numbers once Rholang does? |
There was a problem hiding this comment.
Is this ever in the roadmap?
There was a problem hiding this comment.
Do you mean in the roadmap for Rholang?
| // TODO (chase): Do we need custom options? i.e custom database name, authentication method, and url? | ||
| // If the chroma db is hosted alongside the node locally, custom options don't make much sense. | ||
| let client = ChromaClient::new(ChromaClientOptions::default()) |
There was a problem hiding this comment.
Would custom options for database name, authentication method and URL ever be required? It wouldn't make sense for these to exist if the ChromaDB is being hosted alongside the node in a sort of tightly coupled manner.
There was a problem hiding this comment.
Let's make these configuration options that can be put in shared-rnode-runtime.conf and shared-rnode.conf
There was a problem hiding this comment.
AFAICT the rust impl of Rholang doesn't have any hooks set up with the configurations - the only configurations it seems to take are from the CLI options.
It might be better to wait till the config infra is set up (assuming it's in the works) before adding configs. Otherwise, setting up the config infra will add some time on our end.
| } | ||
|
|
||
| pub trait Extractor<RhoType> { | ||
| pub trait Extractor { |
There was a problem hiding this comment.
This type parameter was entirely redundant. It might have been relevant for Scala, but it's not for Rust.
There was a problem hiding this comment.
I'm suspicious of this... Mind asking about this in the mlabs-sms channel in that Discord group I added you to?
| // these bytes may need to change during finalization. | ||
| pub fn chroma_create_collection() -> Par { | ||
| byte_name(25) | ||
| } | ||
|
|
||
| pub fn chroma_get_collection_meta() -> Par { | ||
| byte_name(26) | ||
| } | ||
|
|
||
| pub fn chroma_upsert_entries() -> Par { | ||
| byte_name(27) | ||
| } |
There was a problem hiding this comment.
These will have to change after nunet implementation has been merged to prevent overlapping bytes.
With that said, the Nunet implementation uses weird byte names. They are not continuous. See: https://github.com/F1R3FLY-io/f1r3node/pull/240/files#diff-0ff9b3c4f760d8d6f04ee13fd2d33f196b7ac795019a91b5bc8202dce9626ecbR162
|
I have added a bunch of runnable examples under Ensure there is a chroma db running locally in the background, as well as |
TotallyNotChase
force-pushed
the
chase/chromadb
branch
from
3c249a5 to
c095011
Compare
|
Added a bunch of tests but they aren't usable until other aforementioned issues with the rust interpreter are fixed. The examples, however, are all runnable. |
Overview
Adds ChromaDB integration to the node as well as primitives to Rholang.
Notes
This will require adding parsers for lists and maps into rho types. Those are currently missing. Some of the argument types for the service will need to be list or maps. Currently, there aren't any system processes/services that require complex types - it seems.
Please make sure that this PR:
Bors cheat-sheet:
bors r+runs integration tests and merges the PR (if it's approved),bors tryruns integration tests for the PR,bors delegate+enables non-maintainer PR authors to run the above.