churromorales commented on issue #15412: URL: https://github.com/apache/lucene/issues/15412#issuecomment-3603540804
Yes! LogTimeRangeMergePolicy would be pretty much what it is. We wanted to roll over indexes originally, but then our clients have a lot of business logic that would require modification to get essentially the same results, albeit rolling indexes would be cleaner and you could have better guarantees of data layout, we noticed this comes pretty close but we didn't need to update client side behavior at all to get a performance boost. This also was kind of an automatic way for us to have lucene do the background work and we didn't need to maintain anything special but some configs we passed to lucene. We had basically X years of data in our segments but only read the last Y timerange, so skipping segments and avoiding paging in and out was a huge boost having them laid out nicely without having to change client behavior at all. Let me know if you are interested, I can put up a PR and we can go from there, no worries either way :) Thanks for the feedback. -- 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]
