Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 27 Jan 2015 19:40:35 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12770191.1422307475000.187298.1422387635287@Atlassian.JIRA>
In-Reply-To: <JIRA.12770191.1422307475000@Atlassian.JIRA>
References: <JIRA.12770191.1422307475000@Atlassian.JIRA>
 <JIRA.12770191.1422307475187@arcas>
Subject: [jira] [Commented] (ACCUMULO-3537) Create an explicit configuration
 option for replacing relative paths
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs commented on ACCUMULO-3537:
---------------------------------------------

I guess what I was trying to say was that we don't really ever need to drop support for these replacements. We don't need to force metadata to be upgraded. We can keep these replacements in indefinitely.

> Create an explicit configuration option for replacing relative paths
> --------------------------------------------------------------------
>
>                 Key: ACCUMULO-3537
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3537
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.7.0
>
>
> {{instance.dfs.uri}} and {{instance.dfs.dir}} were deprecated in as part of ACCUMULO-2061, and were superseded by {{instance.volumes}}.
> This was a little bit confusing, because users upgrading from previous versions would still have relative paths in their metadata. To interpret these relative paths, these deprecated properties must still be set. So, it's a bit confusing to have deprecated properties which are still required for functionality.
> What we should do is explicitly create a way to replace these entries with absolute paths that does not depend on using deprecated properties.
> A sensible location for this is {{instance.volumes.replacements}}. This field could have a special replacement, "RELATIVE", which replaces all relative paths with an explicit target volume. ACCUMULO-3007 ignored relative paths, but this issue proposes to handle them instead of ignore them.
> These properties previously provided two functions:
> # Create new files with absolute paths (only if instance.volumes is not set)
> # Interpret old relative files (always)
> The first function is replaced with {{instance.volumes}}. The second function is replaced by the proposed improvement to {{instance.volumes.replacements}} here.


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