[
https://issues.apache.org/jira/browse/CRUNCH-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029258#comment-14029258
]
Gabriel Reid commented on CRUNCH-418:
-------------------------------------
[~aj987] I guess it would be possible to add a call like
{code}
log.debug(get(PlanningParameters.PIPELINE_PLAN_DOTFILE));
{code}
and then enable debug logging on the category used for that logging call (a
custom logger could be used specifically for that use case). However, I don't
think I really see the added value behind it.
Someone who wants to see that information in their log output then needs to
enable debug logging (at least for the category it was logged under), and even
then I guess to use the information you'd have to go through your log file,
copy the dot contents, and the paste them into a file to create an image out of
it. Is this the use case that you see, or did you have something else in mind?
> Auto-logging Plan
> -----------------
>
> Key: CRUNCH-418
> URL: https://issues.apache.org/jira/browse/CRUNCH-418
> Project: Crunch
> Issue Type: Wish
> Reporter: Allan Shoup
> Priority: Minor
>
> It would be handy if Crunch was capable of logging out the plan DOT diagram
> automatically whenever the pipeline was run.
> By default I would log the plan at a level below INFO - probably at DEBUG.
> Additionally, configuration could be provided to specify the level that the
> plan should be logged at (for example if you always wanted it logged at INFO
> level, or if you wanted to disable logging the plan altogether).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
