gRPC server-streaming RPC as a SQL table.
Why it matters: Microservices teams have RPC as their primary data interface. SQL over gRPC closes the gap between "backend internal data" and "analytics SQL".
Scope (v1): gRPC unary / server-streaming endpoints with reflection-based schema introspection (when the server supports it) or user-supplied .proto. Map proto fields to Arrow types. Filter pushdown via field-mask + request message construction.
Effort: 3-5 days (proto schema → Arrow + the streaming consumer + auth).
gRPC server-streaming RPC as a SQL table.
Why it matters: Microservices teams have RPC as their primary data interface. SQL over gRPC closes the gap between "backend internal data" and "analytics SQL".
Scope (v1): gRPC unary / server-streaming endpoints with reflection-based schema introspection (when the server supports it) or user-supplied .proto. Map proto fields to Arrow types. Filter pushdown via field-mask + request message construction.
Effort: 3-5 days (proto schema → Arrow + the streaming consumer + auth).