Stanislav Jordanov wrote:
After all, the Lucene's CFS format is abstraction over the OS's native
FS and the App should not be trying to open a native FS file named *.fnm
when it is supposed to open the corresponding *.cfs file and "manually"
extract the *.fnm file from it.
Right?
Yes, good catch :)
This always confuses people, but it's actually "normal" (when a segments
file is missing) because Lucene first checks whether the compound-file
exists and if it does it will use that. If it does not, it falls back
to trying to directly open the individual files against the filesystem.
So, when there is a problem and a given segment is referenced but does
not exist, you will see this [confusing] exception making it look like
Lucene "forgot" that it's using the compound file format.
[Still intending to respond to your previous email but a bit busy right
now...]
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
