[ https://issues.apache.org/jira/browse/LUCENE-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Willnauer updated LUCENE-4537: ------------------------------------ Attachment: LUCENE-4537.patch here is a new patch detaching RateLimiting entirely from Directory and it's subclasses. RateLimitingDirectoryWrapper creates an IndexOutput wrapper if it knows of a Ratelimiter for the IOContext the IndexOutput is created for. RateLimitingIndexOutput subclasses BufferedIndexOutput and forwards / pauses on flush to the underlying IndexOutput. I also added an optimiztion for a Wrapped BufferedIndexOutput so FSDir uses will have the same experience as they had before just in a cleaner way API wise. > Move RateLimiter up to Directory and make it IOContext aware > ------------------------------------------------------------ > > Key: LUCENE-4537 > URL: https://issues.apache.org/jira/browse/LUCENE-4537 > Project: Lucene - Core > Issue Type: Improvement > Components: core/store > Affects Versions: 4.0 > Reporter: Simon Willnauer > Fix For: 4.1, 5.0 > > Attachments: LUCENE-4537.patch, LUCENE-4537.patch, LUCENE-4537.patch, > LUCENE-4537.patch > > > Currently the RateLimiter only applies to FSDirectory which is fine in > general but always requires casts and other dir. impls (custom ones could > benefit from this too.) We are also only able to rate limit merge operations > which limits the functionality here a lot. Since we have the context > information what the IndexOutput is used for we can use that for rate > limiting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org