Pavel Korchagin

That's actually doesn't looks like a trivial task, and changing a core functionality just for having a progress bar in a client... not very inspiring :) I hope there will...

Humm. Possibly i don't understand correctly what is "valid" retention config in this case. Here is my configuration ``` SELECT * FROM system.graphite_retentions Query id: b3b2f340-71fe-4b5d-851c-f4ebd664beb7 ┌─config_name─────┬─regexp─┬─function─┬─age─┬─precision─┬─priority─┬─is_default─┬─Tables.database─┬─Tables.table───┐ │ graphite_rollup │...

No problems, i haven't sleep enough as well and thought i was missing something :sweat_smile: Yeah, for backward compatibility this logic can be added by additional setting

I also stepped on it. Despite the unclear error message, this result is cached for more than confugured cache TTL For example, i'm setting 60s for the cache TTL and...

> to protect Clickhouse from fatal queries (unrecoverable). This is a good point, but there are a big question how to separate recoverable and unrecoverable queries. Also, if unrecoverable queries...

+1 It will allow us to make integrations more flexible. For example, we have our own SMS backend, so it would be nice to trigger a webhook with a variable,...

Would like to have this feature as well!

@orloffv Downsize is kinda tricky operation, there are many things that could go wrong. I think it would be better to request/implement it via separated feature request

> Hello @PhantomPhreak, the imagePullSecret should be tied to the serviceaccount Hi @armru, does it mean some additional operator configuration is required?