I think that this is all available, it's just not the easiest thing to get
at. If you look at the explain plan, it has a lot of this info, and you can
definitely get at that info. I'm not sure if it has the reducers or if
that's post MR setup, but you should be able to.
That said, I do not think it would hurt to have hooks in to more clearly do
something with this info. Bill had to do stuff like this for Ambrose, so
maybe he can weigh in on what that could look like.
2013/1/22 Prashant Kommireddi <[EMAIL PROTECTED]>
> Jon/others - any pointers on this? I would like to patch in hooks if this
> is not possible at the moment.
> On Mon, Jan 21, 2013 at 5:47 PM, Prashant Kommireddi <[EMAIL PROTECTED]
> > At the moment, basically info on I/O paths, operators used (group by,
> > foreach ..), job level info such as number of reducers etc.
> > On Mon, Jan 21, 2013 at 5:30 PM, Jonathan Coveney <[EMAIL PROTECTED]
> >> What level of information would you like? IE if you do "explain
> >> which of the three do you want to hook into?
> >> 2013/1/21 Prashant Kommireddi <[EMAIL PROTECTED]>
> >> > Been coding with the APIs and wondering if there is anything that
> >> > you to only retrieve the operators, I/O paths etc without actually
> >> issuing
> >> > an execute or a store? Basically, being able to get information
> >> > post-parsing of the script but pre-execution.
> >> >
> >> > Thanks,
> >> > Prashant
> >> >