[
https://issues.apache.org/jira/browse/ACCUMULO-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070674#comment-14070674
]
Keith Turner commented on ACCUMULO-3007:
----------------------------------------
Before posting this patch, I tested it at my desk by doing the following.
# Start new 1.5.1 instance, create table, add data
# Shutdown 1.5.1
# Start 1.6.1-SNAPSHOT
# Shutdown 1.6.1-SNAPSHOT
# move /accumulo to /up in hdfs
# set instance.volumes and instance.volumes.replacements in accumulo config
# start 1.6.1-SNAPSHOT
# verify I can scan table (does not work before patch)
Also [~dlmarion] tried this patch w/ success on the system where he initially
saw the problem.
It does not seem there is an easy way to test this automatically. I am going
to apply the patch soon unless anyone has suggestions for testing.
> instance.volumes.replacements does not work after 1.6 upgrade
> -------------------------------------------------------------
>
> Key: ACCUMULO-3007
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3007
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Dave Marion
> Assignee: Keith Turner
> Priority: Blocker
> Fix For: 1.6.1, 1.7.0
>
> Attachments: ACCUMULO-3007-1.patch
>
>
> the code behind instance.volumes.replacements does not work with relative
> paths, only absolute paths. New tables created after the upgrade have a
> directory entry in the metadata table with an absolute path, but upgraded
> tables do not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
