You could keep multiple writers opened and it will do no harm. I am doing this.
Its good to reopen (close and open) the writer at certain interval. This will release the memory it holds. Whenever i create a new database, I reopen writers belong to all database. Regards Ganesh ----- Original Message ----- From: "Hrishikesh Agashe" <[email protected]> To: <[email protected]>; <[email protected]> Sent: Monday, November 16, 2009 9:44 AM Subject: RE: Max number of open IndexWriters > Simon and Eric, thanks for the reply. > > I want to create multiple indexes depending on the data present. Like if > month of record is Nov, I want to add it in index for November. If it's > October, add it in index for October. I don't want to open and close indexes > so many times so just maintaining IndexWriters for months in HashMap. > Is there better way of doing this? > > --Hrishi > > -----Original Message----- > From: Simon Willnauer [mailto:[email protected]] > Sent: Sunday, November 15, 2009 5:34 AM > To: [email protected] > Subject: Re: Max number of open IndexWriters > > In general you should only use one single writer and use it with > multiple threads. IndexWriter is optimized for concurrency and fully > thread-safe. Is that what you trying to achieve? > > otherwise I would 100% agree with eric not knowing of a use-case. > > simon > > On Sun, Nov 15, 2009 at 12:58 AM, Erick Erickson > <[email protected]> wrote: >> Hmmm, why would you want to do this? What problem are >> you trying to address with so many readers? >> >> I ask because I'm having a hard time thinking of a reasonable >> use-case. >> >> Best >> Erick >> >> On Sat, Nov 14, 2009 at 11:35 AM, Hrishikesh Agashe < >> [email protected]> wrote: >> >>> Is there any limit on how many IndexWriter can I keep open at same time? >>> What does it depends on (RAM?) Can I keep 100 or 200 IndexWriters open in >>> say HashMap and use them as I process documents? >>> >>> >>> DISCLAIMER >>> ========== >>> This e-mail may contain privileged and confidential information which is >>> the property of Persistent Systems Ltd. It is intended only for the use of >>> the individual or entity to which it is addressed. If you are not the >>> intended recipient, you are not authorized to read, retain, copy, print, >>> distribute or use this message. If you have received this communication in >>> error, please notify the sender and delete all copies of this message. >>> Persistent Systems Ltd. does not accept any liability for virus infected >>> mails. >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is the > property of Persistent Systems Ltd. It is intended only for the use of the > individual or entity to which it is addressed. If you are not the intended > recipient, you are not authorized to read, retain, copy, print, distribute or > use this message. If you have received this communication in error, please > notify the sender and delete all copies of this message. Persistent Systems > Ltd. does not accept any liability for virus infected mails. > Send instant messages to your online friends http://in.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
