accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3537) Create an explicit configuration option for replacing relative paths
Date Tue, 27 Jan 2015 16:25:36 GMT

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

Josh Elser commented on ACCUMULO-3537:
--------------------------------------

bq. I don't think this is that complex of a value. It's a comma separated old=new. And, I
don't think this is really that special

I would disagree with you. The vast majority of our configuration properties are a single
token (class name, fs path, some value). We have a few which accepts a comma-separated list
of single-token items. The old=new introduces a new facet.

bq. The purpose and scope of any new property would be precisely the same as this existing
property

I don't see the existing volume replacement property as synonymous with a new property. The
former is for replacing a portion of an absolute URI (volume). The latter would be for the
specific case of qualifying relative paths. Including a new property makes for "cleanup" of
the Property/docs easier when we start enforcing that relative paths no longer exist.

> 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