[
https://issues.apache.org/jira/browse/ACCUMULO-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852325#comment-13852325
]
Josh Elser commented on ACCUMULO-2061:
--------------------------------------
I do want to note that you are increasing the the configuration complexity for
"common" users now. Currently, instance.dfs.uri doesn't need to be specified
(and will be pulled out of hdfs-site.xml if on the classpath) which lets me
make a new installation by only specifying the HDFS directory I want to use
with instance.dfs.dir.
Can I specify a path only in instance.volumes instead of URI to maintain
backwards compatibility with configurations?
> 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)
