gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alfonso Nishikawa <alfonso.nishik...@gmail.com>
Subject Re: [EARLY WARNING] Possible Major Bug in gora-cassandra
Date Thu, 26 Feb 2015 11:31:55 GMT
Hi, Lewis.

I checked the links but I can't get into a conclusion.
I think we would need to have the output of readdb after each phase:

nutch inject
readdb
nuch generate
readdb
nutch fetch
readdb
nutch parse
readdb
nutch updatedb
readdb

And then much probably we could find something.

Thanks!

Alfonso Nishikawa

2015-02-26 0:46 GMT+01:00 Lewis John Mcgibbney <lewis.mcgibbney@gmail.com>:

> Hi Folks,
> Several threads have popped up over on the Nutch mailing lists regarding
> use of gora-cassandra 0.5 within Nutch 2.3.
>
> http://www.mail-archive.com/user%40nutch.apache.org/msg13228.html
> http://www.mail-archive.com/user%40nutch.apache.org/msg13235.html
> http://www.mail-archive.com/user%40nutch.apache.org/msg13237.html
> http://www.mail-archive.com/user%40nutch.apache.org/msg13250.html
>
> I think we can expect a 0.6.1 release pretty soon if this is discovered to
> be a major bug.
> I have not been using gora-cassandra for a number of months (2 or so), so I
> am not immediately sure right now what is wrong.
> We appear to be loosing data between ParserJob and FetcherJob states with 0
> Map input records being provided to the ParserJob Map Reduce framework.
> Any help from this team on deploying a test configuration and testing would
> be highly appreciated.
> Suggested software stack is as follows
>
> Nutch 2.4-SNAPSHOT (HEAD)
> Gora 0.5, Gora Cassandra 0.5
> Cassandra 2.0.2
>
> Thanks
> Lewis
>
>
> --
> *Lewis*
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message