churromorales opened a new issue, #15412: URL: https://github.com/apache/lucene/issues/15412
### Description As far as I can tell, Lucene doesn’t currently have a date‑tiered merge policy. I’m considering adding one to better support temporal queries over recent time windows. On our larger clusters we see frequent paging of index data in and out of the cache. While most users write in temporal order—and TieredMergePolicy often produces a layout similar to what a date‑tiered approach would—it can still create segments with overlapping time ranges. I’m proposing a time‑aware merge policy, similar in spirit to the “date‑tiered compaction” described here: https://engineering.atspotify.com/2014/12/date-tiered-compaction/ I’d appreciate guidance on two points: 1. 1. Is this feasible and something the community would want? 2. Is it worthwhile, or do current features/configurations already achieve something similar? If this is something interesting to the community, I am happy to write up a design doc and work on this task. Thanks -- 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]
