|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
1) increse the max
2) allow subclasses to override the max
A better solution would be avoid the reason that the max should be kept low.
It seems the limit is there, since for each roll, where maxIndex=N, there are N file renames, and this doesn't scale well up to 100 renames. (Well actually it depends on the filesystem)
I guess users don't care that for max=10, that files are named 1..10. All they really care about is that there are no more than 10 files. So perhaps we could add a mode where we don't rename. Does that make sense? In this non-renaming mode we'd just keep incrementing the index, and deleting files outside the window, but don't rename any files.