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] [Comment Edited] (ACCUMULO-2061) Deprecate instance.dfs.uri and instance.dfs.dir
Date Thu, 19 Dec 2013 00:20:07 GMT

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

Christopher Tubbs edited comment on ACCUMULO-2061 at 12/19/13 12:19 AM:
------------------------------------------------------------------------

After some discussion with [~kturner], I realize it may need to be clarified that the default
behavior should be to fall back on whatever the old fields did, if {{instance.volumes}} is
not specified. Semantically, a default value of "/accumulo" for the new property is the same
behavior as the old properties' defaults. If a user doesn't specify anything in the new property,
it should default to reading the old properties, but if they actually specified anything here,
to include "/accumulo", that needs to comply with the new behavior, and ignore the old properties
(except for interpreting relative paths for upgrade).

(Note: this might require that we be able to tell the difference between a default value of
"/accumulo" and a user-specified value of "/accumulo").


was (Author: ctubbsii):
After some discussion with [~kturner], I realize it may need to be clarified that the default
behavior should be to fall back on whatever the old fields did, if {{instance.volumes}} is
not specified. Semantically, a default value of "/accumulo" for the new property is the same
behavior as the old properties' defaults. If a user doesn't specify anything in the new property,
it should default to reading the old properties, but if they actually specified anything here,
to include "/accumulo", that needs to comply with the new behavior, and ignore the old properties
(except for interpreting relative paths for upgrade).

> Deprecate instance.dfs.uri and instance.dfs.dir
> -----------------------------------------------
>
>                 Key: ACCUMULO-2061
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2061
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Christopher Tubbs
>             Fix For: 1.6.0
>
>
> {{instance.dfs.uri}} and {{instance.dfs.dir}} are no longer needed with the {{instance.volumes}}
property.
> Together, these two fields are needed for upgrades from relative paths, but full URIs
for volumes should be specified in the {{instance.volumes}} set.
> Instead of appending {{instance.dfs.dir}} to every volume, which is a bit confusing,
they should be specified explicitly in the {{instance.volumes}}.
> Example:
> {code}
>  <property>
>     <name>instance.volumes</name>
>     <value>hdfs://nn1/accumulo</value>
>   </property>
> {code}
> should be equivalent to
> {code}
>  <property>
>     <name>instance.dfs.uri</name>
>     <value>hdfs://nn1</value>
>   </property>
>  <property>
>     <name>instance.dfs.dir</name>
>     <value>/accumulo</value>
>   </property>
> {code}
> This change simplifies the semantics of configuring volumes for Accumulo to use for storage,
and is a bit more obvious that we're logically configuring filesystem volumes, not "namenode
URIs".



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message