[
https://issues.apache.org/jira/browse/ACCUMULO-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292859#comment-14292859
]
Josh Elser commented on ACCUMULO-3023:
--------------------------------------
If we are going to do this automatically as a part of the 1.7.0 upgrade (read
as the first time a 1.7.0 master is started on an instance?), what kind of
fail-safes do we need?
What happens if the user provides a bad value for the proposed configuration
value from ACCUMULO-3537? Should we provide some tool that allows dry-runs?
Make sure that the resulting fully-qualified path exists before writing it back
to the metadata table?
> Remove relative paths from internal metadata
> --------------------------------------------
>
> Key: ACCUMULO-3023
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3023
> Project: Accumulo
> Issue Type: Sub-task
> Affects Versions: 1.6.0
> Reporter: Keith Turner
> Fix For: 1.7.0
>
>
> The 1.7.0 upgrade process should remove all relative paths from internal
> Accumulo metadata. This will allow instance.dfs.uri and instance.dfs.dir to
> be dropped in 1.8.0, making things a little less confusing for users. This
> will also allow all code for dealing with relative paths to be dropped in
> 1.7.0, simplifying maintenance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
