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] [Updated] (CRUNCH-537) Deprecate use of PlanningParameters.PIPELINE_PLAN_DOTFILE
Date Thu, 02 Jul 2015 20:12:05 GMT

     [ https://issues.apache.org/jira/browse/CRUNCH-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gabriel Reid updated CRUNCH-537:
--------------------------------
    Attachment: CRUNCH-537.patch

Patch to deprecate PIPELINE_PLAN_DOTFILE.

Probably more importantly, I noticed the mispelled DotfileUtills class name, so renamed it
to DotfileUtil, and deprecated DotfileUtills (and it delegates to DotfileUtil). The deprecation
is for backwards compatibility. Any thoughts on whether I'm a) being too picky about spelling
or b) worrying too much about backwards compatibility?

> Deprecate use of PlanningParameters.PIPELINE_PLAN_DOTFILE
> ---------------------------------------------------------
>
>                 Key: CRUNCH-537
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-537
>             Project: Crunch
>          Issue Type: Improvement
>            Reporter: Gabriel Reid
>         Attachments: CRUNCH-537.patch
>
>
> In some cases, storing the (potentially large) job plan dotfile in the job Configuration
object can cause some issues. Additionally, we now have a much better way of dealing with
the dotfiles (by making it possible to simply set a directory where they will be written).
> We should deprecate {{PlanningParameters.PIPELINE_PLAN_DOTFILE}}, and remove it in another
release or two. Instead of using the Configuration object to pass back the dotfile, the writing
of dotfiles to an output directory should be the standard way of handling dot files.
> Related user list thread: http://s.apache.org/blH



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message