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
Sometimes due to third party errors in qryn, assets are written from the future, for example from the year 2147, and these logs can be many, and the year can be random.
If an asset is too old, it will be deleted by TTL clickhouse, but the future assets will be written to the new clickhouse partition, which may result in a lot of partitions and directly affect performance.
It would be nice to have a flag configured to drop these assemblies on the qryn side, because removing them from the clickhouse can be problematic.
So it would be great to have parameters like:
reject_future_samples: true|false (false by default)
reject_future_samples.max_future_time: 1h|1d|1w|1y (..etc)
The text was updated successfully, but these errors were encountered:
Sometimes due to third party errors in qryn, assets are written from the future, for example from the year 2147, and these logs can be many, and the year can be random.
If an asset is too old, it will be deleted by TTL clickhouse, but the future assets will be written to the new clickhouse partition, which may result in a lot of partitions and directly affect performance.
It would be nice to have a flag configured to drop these assemblies on the qryn side, because removing them from the clickhouse can be problematic.
So it would be great to have parameters like:
reject_future_samples: true|false (false by default)
reject_future_samples.max_future_time: 1h|1d|1w|1y (..etc)
The text was updated successfully, but these errors were encountered: