Thanks for the reply (and thanks for everything else too !!) Mike. I am unable to understand when to call commit. Should I start counting the number of documents I am ingesting and then say every 10 million docs do a commit()? I dont want to do a commit too frequently cause that does not sound correct. Since the ingest velocity is variable, the best thing would have been if I could have this commit() happen when say X number of docs are written. I will try and see if I could find a way to find a good time to commit.
thanks again. Shouvik On Tue, Nov 4, 2014 at 10:47 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > Call commit. > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Nov 4, 2014 at 8:28 AM, Shouvik Bardhan <sbard...@gisfederal.com> > wrote: > > Apologies if this is trivial but I have read what I could on the net and > > could not come up with a good answer. > > > > I have stood up a lucene server (not solr) which listens on 2 ports - one > > for indexing and one for search. Also on different threads. The indexer > > threads use one IndexWriter and the searcher threads get the > > SearcherManager from the Indexwriter and does maybereopen() to refresh > from > > time to time. > > > > When I run this and pump indexing data into it, I see index files in the > > directory coming in fast and furious but I dont see a segment file. I > guess > > that is because I dont call close or commit on the IW. My question is > what > > should I do so that every so often new segments are written? Data is > > getting flushed to the disk but there is no Segment info being written. I > > must be missing something. > > > > thanks for all the help guys, > > Shouvik > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
