Hello Druid devs, With Druid sql slowly becoming the de-facto way of issuing Druid queries, chances of user queries unintentionally doing too much and potentially putting a lot of load on the the Druid cluster goes up. One such case being users forgetting to limit the amount of data they are scanning by forgetting to add appropriate filter on the __time column.
Does it make sense to start investing in service protection features which provides operators ways to throttle/block such queries from running. At my work, for example, we are enabling druid sql on our platform. And to make sure users get a good experience, I am adding a check to block queries if the "intervals" part of query is unbounded. - Samarth
