crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-418) Auto-logging Plan
Date Thu, 12 Jun 2014 18:51:02 GMT

    [ https://issues.apache.org/jira/browse/CRUNCH-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029598#comment-14029598
] 

Gabriel Reid commented on CRUNCH-418:
-------------------------------------

{quote}I'm assuming not everyone would want that amount of content written to the log every
time{quote}
Yeah, me too -- for that reason, I would say that if it's logged at all then it should be
logged as debug. However, it feels to me like this doesn't belong in logging. I see logging
as human-readable information to know what a application is doing, so having something that
is basically not human readable being logged with the intention of copying and pasting it
into another file for processing feels wrong to me.

What I typically do is something like this:
{code}Files.write(conf.get(PlanningParameters.PIPELINE_PLAN_DOTFILE), new File("jobplan.dot"),
Charsets.UTF_8);{code}

Is that an option for you?

> 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)

Mime
View raw message