Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Use TimeWindowCompactionStrategy on keyspace initialization and TTL config
Description
When running newts init the keyspace for samples the compaction strategy is unconfigured and falls back to defaults. The result is the samples table is initialized with Size Tiered Compaction Strategy which is not optimal for time series data. The Time Window Compaction Strategy is a better choice and should be used instead.
We have some compaction strategy configuration which depends on the TTL
compaction_window_size
compaction_window_unit
expired_sstable_check_frequency_seconds
It would be helpful to allow an administrate these schema properties when the keyspace is initialized.
*Optional*, We should investigate to set the write-order for collected_at from default ASC to DESC explicitly to have the newest samples always at the end. This could also save us a sort later when data is queried for rendering the time-series graph in the UI or querying measurement through the Measurements REST API.
When running
newts initthe keyspace for samples the compaction strategy is unconfigured and falls back to defaults. The result is the samples table is initialized with Size Tiered Compaction Strategy which is not optimal for time series data. The Time Window Compaction Strategy is a better choice and should be used instead.We have some compaction strategy configuration which depends on the TTL
compaction_window_size
compaction_window_unit
expired_sstable_check_frequency_seconds
It would be helpful to allow an administrate these schema properties when the keyspace is initialized.
*Optional*, We should investigate to set the write-order for
collected_atfrom default ASC to DESC explicitly to have the newest samples always at the end. This could also save us a sort later when data is queried for rendering the time-series graph in the UI or querying measurement through the Measurements REST API.