You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2026/02/17 23:02:00 UTC
[jira] [Commented] (CASSANDRA-21178) Introduce created_at column to system_distributed.compression_dictionaries
[ https://issues.apache.org/jira/browse/CASSANDRA-21178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059212#comment-18059212 ]
Stefan Miklosovic commented on CASSANDRA-21178:
-----------------------------------------------
https://pre-ci.cassandra.apache.org/job/cassandra/401/#showFailuresLink
> Introduce created_at column to system_distributed.compression_dictionaries
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-21178
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21178
> Project: Apache Cassandra
> Issue Type: Task
> Components: Feature/Compression
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Rationale:
> 1) A user does not know when a training occurred so they can not evaluate if they shoul train again.
> 2) A user could implement "poor's man auto training" just by croning it.
> 3) At the same time, we do not want to "over train", that is, we do not want to allow a user to train, for example, 100 times per minute as that does not make any sense. If we introduce created_at column with a timestamp, then we could say that not enough time elapsed since the last training and such operation would be failed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org