Right. If your use case boils down to a join, we're probably not the ideal
tool.
On Tue, Jan 29, 2013 at 1:26 AM, Claudio Martella <
claudio.marte...@gmail.com> wrote:
> That is correct, but that is not the reason. We use M/R for resource
> allocation, but we do not inherit the limits of the M/R
Quite honestly I do not believe it is connected with ZK, it is quite weird
that it does not pass tests in pseudo-distributed mode... I think it is
quite serious that we cannot run tests on 1.0 not even in
pseudo-distributed mode. I honestly do not know when the bug was
introduced. I think IT MIGHT
That is correct, but that is not the reason. We use M/R for resource
allocation, but we do not inherit the limits of the M/R paradigm for
graphs. The thing is that you probably have a lot of data (I assume it
because you are using HBase, hence it is difficult for you to fit it all
into memory), and
Hello Claudio and Eli,
Thank you for your answers. As far as Map/Reduce being a better tool for
the job - I was under the impression that Giraph relies on the M/R
framework. It seems like it when I check the console output of the examples
on the project's Wiki.
Again, thank you.
/David
On Mon,
