Additional stream/4 function to allow the client to set the bucket resolution on stream write. Wasn't sure how to overcome the duplication between added function and stream/3 variant. Also, when a different resolution is set to a pre-existing resolution, an error is not signalled to the client. This is similar behaviour to when a point is written that cannot dproto:decode on write .
Additional
stream/4
function to allow the client to set the bucket resolution on stream write. Wasn't sure how to overcome the duplication between added function andstream/3
variant. Also, when a different resolution is set to a pre-existing resolution, an error is not signalled to the client. This is similar behaviour to when a point is written that cannotdproto:decode
on write .Relates to https://github.com/dalmatinerdb/dalmatinerdb/issues/64