Yusuf Ozturk

Okay this is my first test results on a small machine on DigitalOcean: **100.000 records** HTTP Client with Avro format (file is around 5.5 MB) Write took 16.0331926s Clickhouse-go Write...

@gingerwizard What I planned so far: (this is my plan. didn't do any of it yet. I'm not sure if everything will go as plan.) 1. Write a serializer/deserializer for...

@gingerwizard at the end, we decided to go with clickhouse-go. We used following method in ch-go: ``` err := c.Do(ctx, ch.Query{ Body: sql.GetInsertQuery() + " VALUES", Input: input, }) ```...

Also I was thinking encode and compress native format and giving it directly to the clickhouse-go. That would also save us from some conversion latency. But I don't know how...

@gingerwizard yes, (1) would be perfect! Actually if you bring the (1), nobody stops you at the Avro anymore. Basically any supported format by Clickhouse would be supported, right? So...

@gingerwizard it would be perfect if library can support streams so instead of putting entire avro file into the memory, we can send to Clickhouse via reader. (I'm also going...

SO_REUSEPORT and SO_REUSEADDR is supported on Windows as well. Here is the screenshot on Windows:  I was able to listen same port from multiple threads. Looking forward to see...

I think in general using Epoch value is much safer. Quartz returns an interval value which is a total number of nanoseconds/milliseconds/seconds etc. So taking Epoch value as an input...

A similar issue when timezone is in place: https://github.com/reugn/go-quartz/issues/33

@gengquanying I didn't test yet but fourth one is Next Sunday (2022-07-03 18:32:00) and third one is Next Monday (2022-07-04 18:32:00). So I feel like it's correct.