jtuglu1 opened a new issue, #18602: URL: https://github.com/apache/druid/issues/18602
### Description Want to support result-set caching of queries hitting realtime data nodes. Want to create a way to partition the result set of a query (from either realtime/historical data nodes) into cacheable granular intervals that can either pulled from cache and stitched into the query result, or issued as a query to data nodes. Providing a TTL content header would dictate how "recent" of an interval we'd want to serve from cache, versus hitting realtime nodes. Something like `cacheTTL: "PT1M"` would tell the brokers to serve from cache all results that were > PT1M ago, and issue queries to data nodes for data <PT1M. ### Motivation This would allow for result-set caching of queries against realtime segments, significantly boosting performance while potentially trading off staleness of data, configurable by the user. For longer-running stream ingestion jobs (e.g. where a realtime segment contains last 1h of data) the "staleness" imposed by this feature would likely be negligible, assuming low-to-no late records. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
