OK guys, upgrade to Upgrade to Hadoop
1.0.3<https://issues.apache.org/jira/browse/NUTCH-1401>done for
NutchGora +
NUTCH-1404 <https://issues.apache.org/jira/browse/NUTCH-1404> committed for
trunk and NutchGora

Have marked NUTCH-1400 for 1.5.1 release - feel free to take this one

Thanks

Jul

On 19 June 2012 14:08, Julien Nioche <lists.digitalpeb...@gmail.com> wrote:

> Tracking on https://issues.apache.org/jira/browse/NUTCH-1404
>
>
> On 19 June 2012 14:04, Julien Nioche <lists.digitalpeb...@gmail.com>wrote:
>
>> Yep, am working on fixing it for both 1.5.1 and 2.0. Will let you know
>> when done
>>
>>
>> On 19 June 2012 13:59, Lewis John Mcgibbney <lewis.mcgibb...@gmail.com>wrote:
>>
>>> Guys this will also be the case for 2.0...
>>>
>>> The naming convention changed and I introduced this bug when I committed
>>> it.
>>>
>>> We need to spin 1.5.1 RC#1 and 2.0 RC#3
>>>
>>> Lewis
>>>
>>> On Tue, Jun 19, 2012 at 1:13 PM, Mattmann, Chris A (388J)
>>> <chris.a.mattm...@jpl.nasa.gov> wrote:
>>> > +1!
>>> >
>>> > Cheers,
>>> > Chris
>>> >
>>> > On Jun 19, 2012, at 2:26 AM, Julien Nioche wrote:
>>> >
>>> >> Quite annoying that we did not spot this before releasing. What about
>>> a 1.5.1 soonish with this fix + couple smallish improvements e.g. upgrade
>>> to Hadoop 1.0.3?
>>> >>
>>> >> J.
>>> >>
>>> >> ---------- Forwarded message ----------
>>> >> From: Julien Nioche <lists.digitalpeb...@gmail.com>
>>> >> Date: 19 June 2012 08:56
>>> >> Subject: Re: Nutch 1.5 Deploy Mode Doesn't Work like Nutch 1.4 Deploy
>>> Mode
>>> >> To: u...@nutch.apache.org
>>> >>
>>> >>
>>> >> Alternatively modify the bin/nutch script to make it more robust
>>> >>
>>> >> # NUTCH_JOB
>>> >> if [ -f ${NUTCH_HOME}/*nutch*.job ]; then
>>> >>     local=false
>>> >>   for f in $NUTCH_HOME/*nutch*.job; do
>>> >>     NUTCH_JOB=$f;
>>> >>   done
>>> >> fi
>>> >>
>>> >> On 19 June 2012 00:09, sidbatra <siddharthaba...@gmail.com> wrote:
>>> >> This turns out to be a genuine bug with an easy fix.
>>> >>
>>> >> build.xml is configured to generate a job file titled
>>> "apache-nutch-1.5.job"
>>> >> but the deploy binary is still looking for "nutch-1.5.job"
>>> >>
>>> >>
>>> >> Renaming "apache-nutch-1.5.job" to "nutch-1.5.job" fixes this bug in
>>> deploy
>>> >> mode.
>>> >>
>>> >> --
>>> >> View this message in context:
>>> http://lucene.472066.n3.nabble.com/Nutch-1-5-Deploy-Mode-Doesn-t-Work-like-Nutch-1-4-Deploy-Mode-tp3990169p3990196.html
>>> >> Sent from the Nutch - User mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> Open Source Solutions for Text Engineering
>>> >>
>>> >> http://digitalpebble.blogspot.com/
>>> >> http://www.digitalpebble.com
>>> >> http://twitter.com/digitalpebble
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> Open Source Solutions for Text Engineering
>>> >>
>>> >> http://digitalpebble.blogspot.com/
>>> >> http://www.digitalpebble.com
>>> >> http://twitter.com/digitalpebble
>>> >>
>>> >
>>> >
>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> > Chris Mattmann, Ph.D.
>>> > Senior Computer Scientist
>>> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> > Office: 171-266B, Mailstop: 171-246
>>> > Email: chris.a.mattm...@nasa.gov
>>> > WWW:   http://sunset.usc.edu/~mattmann/
>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> > Adjunct Assistant Professor, Computer Science Department
>>> > University of Southern California, Los Angeles, CA 90089 USA
>>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> >
>>>
>>>
>>>
>>> --
>>> Lewis
>>>
>>
>>
>>
>> --
>> *
>> *
>> Open Source Solutions for Text Engineering
>>
>> http://digitalpebble.blogspot.com/
>> http://www.digitalpebble.com
>> http://twitter.com/digitalpebble
>>
>>
>
>
> --
> *
> *Open Source Solutions for Text Engineering
>
> http://digitalpebble.blogspot.com/
> http://www.digitalpebble.com
> http://twitter.com/digitalpebble
>
>


-- 
*
*Open Source Solutions for Text Engineering

http://digitalpebble.blogspot.com/
http://www.digitalpebble.com
http://twitter.com/digitalpebble

Reply via email to