Re: is the classes ended with PerThread(*PerThread) multithread

2010-12-28 Thread Earwin Burrfoot
There is a single indexchain, with a single instance of each chain component, except those ending in -PerThread. Though that's gonna change with https://issues.apache.org/jira/browse/LUCENE-2324 On Tue, Dec 28, 2010 at 13:10, Simon Willnauer wrote: > On Tue, Dec 28, 2010 at 10:57 AM, xu cheng w

Re: is the classes ended with PerThread(*PerThread) multithread

2010-12-28 Thread Simon Willnauer
On Tue, Dec 28, 2010 at 10:57 AM, xu cheng wrote: > hi simon > thanks for replying very much. > after reading the source code with your suggestion, here's my understanding, > and I don't know whether it's right: > the DocumentsWriter actually don't create threads, but the codes that use > Document

Re: is the classes ended with PerThread(*PerThread) multithread

2010-12-28 Thread xu cheng
hi simon thanks for replying very much. after reading the source code with your suggestion, here's my understanding, and I don't know whether it's right: the DocumentsWriter actually don't create threads, but the codes that useDocumentsWriter can do the multithreading(say, several threads call u

Re: is the classes ended with PerThread(*PerThread) multithread

2010-12-28 Thread Simon Willnauer
Hey there, so what you are looking at are classes that are created per Thread rather than shared with other threads. Lucene internally rarely creates threads or subclasses Thread, Runnable or Callable (ParallelMultiSearcher is an exception or some of the merging code). Yet, inside the indexer when

is the classes ended with PerThread(*PerThread) multithread

2010-12-27 Thread xu cheng
hi all: I'm new to dev these days I'm reading the source code in the index package and I was confused. there are classes with suffix PerThread such as DocFieldProcessorPerThread, DocInverterPerThread, TermsHashPerThread, FreqProxTermWriterPerThread. in this mailing-list, I was told that they are m