Apache Druid

A shard spec is something that lives on existing segments (see <https://druid.apache.org/docs/latest/querying/sql-metadata-tables.html>). The interval in your error message is sus `interval[2022-12-10T00:00:00.000-05:00/2022-12-11T00:00:00.000-05:00]` the `-05:00` specifically. Is are your Druid servers not running in UTC timezone?

Also somewhat related: there were a lot of partitioning related improvements in Druid since 0.21.0 such as [multi dim in 0.23.0](<https://imply.io/blog/multi-dimensional-range-partitioning/>) and SQL based ingestion that takes partitioning to another level [introduced in 24.0, GA in 25.0](<https://imply.io/blog/a-new-shape-for-apache-druid/>). If you are playing with partitioning for you could also check out the latest and greatest!

Servers are running in UTC.
We do plan to migrate to the latest version, but this will take some time. This issue is not exactly critical right now, but since I was investigating the other <https://apachedruidworkspace.slack.com/archives/C0309C9L90D/p1673027174429679|issue>, I am considering potential causes for it and thought that `partitionSpec` type might help in that.