I'm working on the lock-less commit patch, and came across what seems to be a bug in the current Lucene sources:
If you have an index that has separate norms (.sN or .fN files), and you open a reader against this index, and then try to use another reader to change (& commit) the norms, that second reader will hit an IOException (Access Denied) on Windows during commit because the first reader is holding open the .sN (or .fN) files. The .del files don't have this issue because they opened, read, and then closed. Has anyone seen this? Maybe the IndexReader.setNorm() API is not typically used when there are other active searchers (on Windows)? Does this sound like a real bug (ie this use case is supposed to work)? I couldn't find anything matching this in Jira. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
