You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Joshua Cohen (JIRA)" <ji...@apache.org> on 2014/10/17 01:17:34 UTC

[jira] [Updated] (AURORA-862) What to do with slave_run_directory in client cluster configuration

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

Joshua Cohen updated AURORA-862:
--------------------------------
    Description: This property is required and has no default. In every (maybe?) scenario, this property will be set to `latest`. We should consider either removing this property entirely and hardcoding it into the client or at the very least making it non-required and setting the default to `latest`.  (was: This property is required and has no default. In every(?) scenario, this property will be set to `latest`. We should consider either removing this property entirely and hardcoding it into the client or at the very least making it non-required and setting the default to `latest`.)

> What to do with slave_run_directory in client cluster configuration
> -------------------------------------------------------------------
>
>                 Key: AURORA-862
>                 URL: https://issues.apache.org/jira/browse/AURORA-862
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Joshua Cohen
>
> This property is required and has no default. In every (maybe?) scenario, this property will be set to `latest`. We should consider either removing this property entirely and hardcoding it into the client or at the very least making it non-required and setting the default to `latest`.



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