Hello All,
I am slightly concerned about using ByteBuffers as means for localizing the
per vertex configuration.
I thought the purpose of the byte buffers were to allow Pig/Hive to send
additional information (not necessarily in the form of Configuration
objects) to the vertices. This seems to defeat the purpose because we are
using it exclusively to deserialize the configuration object for the
vertex.
I am running into this issue at the initialize method of MRRuntimeTask. In
local mode, I am setting some additional configs in the Configuration
object for that vertex and passing that forward, so it should propagate in
the following method:
initialize(Configuration conf, byte[] userPayload,
Master master)
But now I see that I have to instead deserialize the user payload myself,
set the configs there, and then reserialize them. This is not a big change
or anything but it got my thinking.
Thoughts on this would be great!
- Achal
