By the way, even though the commit script returns an error, it actually does send the commit to the Solr server. You can check the Solr server log file to verify that. So you don't need to do anything if you can live with the incorrect return code of the script.
Bill On 9/21/07, Bill Au <[EMAIL PROTECTED]> wrote: > > You should be able to run the latest version of the scripts against Solr > 1.2. Just grab a copy for subversion: > > http://svn.apache.org/viewvc/lucene/solr/trunk/src/scripts/ > > Bill > > On 9/21/07, Yu-Hui Jin <[EMAIL PROTECTED]> wrote: > > > > Got it. So what's the easiest way to get this patch? Sorry i'm new to > > this. > > > > > > regards, > > -Hui > > > > On 9/20/07, Bill Au <[EMAIL PROTECTED]> wrote: > > > > > > That would be my bad. I noticed the problem while fixing SOLR-282 > > > which is not related. I fixed both problems in stead of opening a > > > different bug for the response format issue. I will update the change > > > > > log. > > > > > > Bill > > > > > > On 9/20/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > > > : > > > > : It seems there's a small bug in the bin/commit script for solr 1.2 > > . > > > > > > > > A fix was already commited to the trunk for this as part of SOLR-282 > > > (but > > > > there doesn't seem to be a note about it in the changelog) > > > > > > > > > > > > -Hoss > > > > > > > > > > > > > > > > > > > -- > > Regards, > > > > -Hui > > > >
