Nothing that Giraph does should be influenced by 32/64 (basically,
very rare caveats apply, etc, etc). I'm still not clear on what error
you're encountering. Your custom mapper sets everything GraphMapper
does, but then doesn't run?
On Tue, Feb 7, 2012 at 6:18 PM, David Garcia
That's not necessarily a bad thing. Hadoop (not Giraph) has native
code library it can use for improved performance. You'll see this
message when running on a cluster that's not been deployed to use the
native libraries. If I follow what you wrote, most likely your work
project cluster is so
If you're using GiraphJob, the mapper class should be set for you.
That's weird.
Avery
On 2/7/12 5:58 PM, David Garcia wrote:
That's interesting. Yes, I don't need native libraries. The problem I'm
having is that after I run job.waitForCompletion(..),
The job runs a mapper that is
Yeah. I haven't changed anything with the standard Giraph stuff. I just
made my own vertex and and VertexInputFormat. We are in a 64bit
environment. . .is it possible that building a jar with 32bit tools would
be a problem? I wouldn't think so, since that addressing
native-dependency issues
