You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proton ingesting is built as http rest api, implementing a grpc endpoint would help somewhat safely lift data type limitations.
Even though proton has grpc protocol, it's tuned for querying the data, but not for ingesting.
Describe the solution you'd like
Extra method definition in proton.grpc.Proton service, something like:
// Based on WKT's google.protobuf.StructenumNullValue {
// Null value.NULL_VALUE=0;
}
messageArrayValue {
repeatedDataTypevalues=1;
}
messageMapValue {
map<string, DataType> values=1;
}
messageDataType {
oneofkind {
NullValuenull_value=1;
// Automatic cast to smaller sizesint64int_value=2;
// Automatic cast to smaller sizesuint64uint_value=3;
// For decimal and floatdoubledouble_value=4;
boolbool_value=5;
stringstring_value=6;
// Cast to string on the ingest sidebytesbytes_value=7;
ArrayValuearray_value=8;
MapValuemap_value=9;
}
}
messageIngestInfo {
repeatedstringcolumns=1;
repeatedArrayValuedata=2;
}
serviceProton {
// ...rpcExecuteIngest(IngestInfo) returns (Result) {}
rpcExecuteIngestWithStreamIO(streamIngestInfo) returns (streamResult) {}
}
The text was updated successfully, but these errors were encountered:
Use case
Proton ingesting is built as http rest api, implementing a grpc endpoint would help somewhat safely lift data type limitations.
Even though proton has grpc protocol, it's tuned for querying the data, but not for ingesting.
Describe the solution you'd like
Extra method definition in
proton.grpc.Proton
service, something like:The text was updated successfully, but these errors were encountered: