accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joshelser <...@git.apache.org>
Subject [GitHub] accumulo pull request #120: ACCUMULO-4324 update data version
Date Wed, 13 Jul 2016 14:55:42 GMT
Github user joshelser commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/120#discussion_r70641365
  
    --- Diff: server/base/src/main/java/org/apache/accumulo/server/ServerConstants.java ---
    @@ -68,7 +72,7 @@
       public static final int LOGGING_TO_HDFS = 4;
       public static final BitSet CAN_UPGRADE = new BitSet();
       static {
    -    for (int i : new int[] {DATA_VERSION, MOVE_TO_ROOT_TABLE, MOVE_DELETE_MARKERS, LOGGING_TO_HDFS})
{
    +    for (int i : new int[] {DATA_VERSION, MOVE_TO_REPLICATION_TABLE, MOVE_TO_ROOT_TABLE,
MOVE_DELETE_MARKERS, LOGGING_TO_HDFS}) {
    --- End diff --
    
    1.6 and 1.7 to 1.8 sound like they should both work to me.
    
    My gut reaction is to not worry about 1.5, but is there any fundamental problem in supporting
that (is it just a testing burden)? If we don't support a direct upgrade from 1.5, what's
the fail-safe? Could users just bulk-import the old files into a new instance?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message