[
https://issues.apache.org/jira/browse/ACCUMULO-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913719#comment-13913719
]
Christopher Tubbs commented on ACCUMULO-2061:
---------------------------------------------
I think this issue gets to the heart of how users fundamentally understand how
to interact with this very important new feature. We will not be able to
fundamentally alter this interaction in the future. If we "punt" and do not do
this for this release, it will be a significant burden to do it later. I really
think it should be done for 1.6.0. If not for 1.6.0, then it probably shouldn't
change at all.
> 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
> Assignee: Josh Elser
> Priority: Critical
> 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.5#6160)
