accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3537) Create an explicit configuration option for replacing relative paths
Date Mon, 26 Jan 2015 21:27:34 GMT

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

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

{{instance.volumes.replacements}} may currently have a restriction that the replacement must
exist in {{instance.volumes}}. That may be problematic here, but I'm not sure that restriction
is even needed. {{instance.volumes}} specifies new volumes to use. The volume being replaced
doesn't need to be available for new files. We just need to be able to access the old location.
So, if that restriction is in place, we need to create another issue to relax that restriction.

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

Mime
View raw message