You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/02/06 18:36:34 UTC
[jira] [Commented] (ACCUMULO-3023) Remove relative paths from
internal metadata
[ https://issues.apache.org/jira/browse/ACCUMULO-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309490#comment-14309490 ]
Christopher Tubbs commented on ACCUMULO-3023:
---------------------------------------------
[~kturner] suggested to me that for the offline table case, we could have the Master initiate a fate operation to update those. I was also thinking that a more general solution would be good to bake in to the master, so we can make other tablet metadata updates on occasion.
> 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)