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
In issue #3152 we noticed that we need to support timestamp_resolution = MILLISECONDS in TWCS for KairosDB that uses it (the default is MICROSECONDS). We did this in commit 0c72781.
Cassandra actually allows several other units, not just MICROSECONDS or MILLISECONDS, and although nobody is likely to ever use them (I don't think we ever had complaints from users), we should consider supporting all the units and not just two of them.
Noticed this in #16027 - we had a Scylla test that checks that "SECONDS" isn't supported as timestamp_resolution - but then we noticed that it failed on Cassandra because it is supported on Cassandra.
The text was updated successfully, but these errors were encountered:
…stamp resolutions.
Cassandra supports timestamp resolutions beyond MICROSECONDS and MILLISECONDS for the Time Window Compaction Strategy (all units understandable by Java TimeUnit). To ensure compatibility, we extend the list of supported timestamp resolutions to include seconds, minutes, hours, and days.
Fixesscylladb#16057
Update from discussion in #17269: It appears that the existing code (compaction/time_window_compaction_strategy.cc) in addition to the sub-second units MILLISECONDS and MICROSECONDS, also supported the whole-second units MINUTES, HOURS and DAYS. The full lists of units we need to support is Java's https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/TimeUnit.html - so we're only missing support for SECONDS (this is the problem that started this issue) and NANOSECONDS. The rest should already be fine.
…stamp resolutions.
Cassandra supports timestamp resolutions beyond MICROSECONDS and MILLISECONDS for the Time Window Compaction Strategy (all units understandable by Java TimeUnit). To ensure compatibility, we extend the list of supported timestamp resolutions to include seconds, minutes, hours, and days.
Fixesscylladb#16057
In issue #3152 we noticed that we need to support
timestamp_resolution = MILLISECONDS
in TWCS for KairosDB that uses it (the default isMICROSECONDS
). We did this in commit 0c72781.Cassandra actually allows several other units, not just MICROSECONDS or MILLISECONDS, and although nobody is likely to ever use them (I don't think we ever had complaints from users), we should consider supporting all the units and not just two of them.
Noticed this in #16027 - we had a Scylla test that checks that "SECONDS" isn't supported as timestamp_resolution - but then we noticed that it failed on Cassandra because it is supported on Cassandra.
The text was updated successfully, but these errors were encountered: