Resource Group Tracking Physical Bytes Scan

[kekwan]

Currently, resource groups can limit usage on query concurrency, CPU and memory. We have some use-cases in our company where we want to limit how much data scan each user can do. I am thinking of adding that functionality into resource groups. Would there be interest in this feature or any pushback?

Limiting data scan can have some good cost benefits if you're using cloud object storage e.g. cross region access, pulling excess data from cheaper tiers of storage, etc. Right now the only control we have on data scan is per-query with query.max-scan-physical-bytes