Why is Field.java final?

I was going to create a new IDField class which just calls super( name, value, false, true, false) but noticed I was prevented because Field.java is final? Why is this? I can't see any harm in making it non-final... Kevin -- Please reply using PGP. http://peerfear.org/pubkey.asc

Re: Why is Field.java final?

I was running into the similar problems with Lucene classes being final. In my case the Token class. I sent out an email but no one responeded :( -John On Sat, 10 Jul 2004 15:50:28 -0700, Kevin A. Burton [EMAIL PROTECTED] wrote: I was going to create a new IDField class which just calls super(

Pool of IndexReaders or Pool of Searchers?

Hi, I have multiple threads reading an index. Should they all be using the same IndexReader and using a pool of IndexSearchers? Or should they be using a pool of IndexReaders? Basically, one reader or many? Thanks. -

Re: Pool of IndexReaders or Pool of Searchers?

1 should be sufficient, as IR/IS are thread-safe, I believe. Otis --- [EMAIL PROTECTED] wrote: Hi, I have multiple threads reading an index. Should they all be using the same IndexReader and using a pool of IndexSearchers? Or should they be using a pool of IndexReaders? Basically,