Then replace commit with optimize? curl 'http://localhost:8983/solr/update?optimize=true'
-Yonik http://www.lucidimagination.com On Wed, Aug 12, 2009 at 2:43 PM, KaktuChakarabati<jimmoe...@gmail.com> wrote: > > Hey Yonik, > Thanks for the quick reply, However my first question was more specific: > * I'm not worried about a commit but about the *optimize* operation which I > might want to run very infrequently > in respect to commits ( e.g I can commit every 15 minutes but optimize > once a day ) > > > Yonik Seeley-2 wrote: >> >> A script isn't really needed for something as simple as a commit: >> >> curl 'http://localhost:8983/solr/update?commit=true' >> >> -Yonik >> http://www.lucidimagination.com >> >> On Wed, Aug 12, 2009 at 2:27 PM, KaktuChakarabati<jimmoe...@gmail.com> >> wrote: >>> >>> Hey, >>> I noticed in recent SVN versions the example/solr/bin dir has been empty. >>> I understand the various snappulling scripts are basically deprecated >>> since >>> replication is now handled in-process, however I was wondering what is >>> the >>> state of the >>> optimize script, i.e how do I control optimization myself? is this also >>> now >>> taken care of in-process? >>> or should i still grab the optimize script ( from src/scripts ) and >>> crontab >>> it? >>> >>> Related question: In the in-procfess replication there is only a >>> pollInterval parameter. However, In some cases >>> I might want to poll often ('snappull' often) but actually install a new >>> search ('snapinstall') less often. >>> It dosent look like its possible with current mechanism? >>> >>> Thanks, >>> -Chak >>> -- >>> View this message in context: >>> http://www.nabble.com/Solr1.4-and-snapinstalling-optimize-script-tp24942205p24942205.html >>> Sent from the Solr - User mailing list archive at Nabble.com. >>> >>> >> >> > > -- > View this message in context: > http://www.nabble.com/Solr1.4-and-snapinstalling-optimize-script-tp24942205p24942475.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
