Replies: 1 comment 2 replies
-
Yes, greptime-ingester-rust is meant to be write-only, as its name suggests
This crate provides rpc interface and stubs for internal communication, eg., from frontend to datanode, and is not exposed to users.
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm building a Rust based data interface that uses a single instance of Greptime standalone. Standalone is running in its own process. I'd like to use a gRPC client from Rust. I'm looking at the Rust ingester example but it looks like that client is configured for write-only (makes sense for ingest only). There's the "client" crate from the main greptimedb project, which appears to be a full blown client. I'd be incline to use that but the crate doesn't seem readily usable as an external library. This may be wrong though - I'm new to Rust!
Given my situation - writing a Rust app that wants to both write to and query a standalone Greptime instance over a socket as efficiently as possible - what would you recommend? I understand there are myriad interfaces available to me (MySQL, Postgres, etc.) but as I'm in Rust already, I'd prefer to use whatever Greptime itself uses when efficiency is of concern.
Any advice is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions