accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3023) Remove relative paths from internal metadata
Date Tue, 27 Jan 2015 16:17:34 GMT


Christopher Tubbs commented on ACCUMULO-3023:

So, I'm not sure how exactly we're going to do this, or if we'll complete it in 1.7.0. Maybe
ACCUMULO-3537 is sufficient and we just recommend bringing tables online so they can have
their metadata updated?

As for dry-runs/checks, we're basically just enforcing "replacements", so it should have all
the same checks as leveraging that property does. Mistakes could be corrected relatively easily
by adding a corrected mapping to the replacements property.

I don't think checking for path existence is scalable, and we don't do any such checks for
path existence while currently using the deprecated properties to resolve these, so I'm not
sure that falls within scope of this.

> Remove relative paths from internal metadata
> --------------------------------------------
>                 Key: ACCUMULO-3023
>                 URL:
>             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

View raw message