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
I have a use case where I want to write the quantile sketch serialized data that is compatible with the ClickHouse server. For example, quantileBFloat16 uses a hash of bfloat16 using Data = HashMapWithStackMemory<BFloat16, Weight, TrivialHash, 4>;. It would be very helpful to send the go type map[uint16]uint64. In this PR we add the DDSketchClickHouse/ClickHouse#56342, which has its own binary representation. The sketches data from systems could come pre-aggregated that can be combined on the ClickHouse server to produce the quantile at the query time by merging them.
I would like to work on add support for AggregateFunction and AggregateFunction(quantilesDDSketch ...)) to begin with. I see the go client library internally uses https://github.com/ClickHouse/ch-go. Let me know what you think.
The text was updated successfully, but these errors were encountered:
I have a use case where I want to write the quantile sketch serialized data that is compatible with the ClickHouse server. For example,
quantileBFloat16
uses a hash of bfloat16using Data = HashMapWithStackMemory<BFloat16, Weight, TrivialHash, 4>;
. It would be very helpful to send the go typemap[uint16]uint64
. In this PR we add theDDSketch
ClickHouse/ClickHouse#56342, which has its own binary representation. The sketches data from systems could come pre-aggregated that can be combined on the ClickHouse server to produce the quantile at the query time by merging them.I would like to work on add support for
AggregateFunction
andAggregateFunction(quantilesDDSketch ...))
to begin with. I see the go client library internally uses https://github.com/ClickHouse/ch-go. Let me know what you think.The text was updated successfully, but these errors were encountered: