From 11356cad9d629311f1a4832bc81857b24a6578d9 Mon Sep 17 00:00:00 2001
From: matthew_swift <matthew_swift@localhost>
Date: Wed, 13 Feb 2008 10:37:33 +0000
Subject: [PATCH] Commit flag day changes for r3873.

---
 opends/src/server/org/opends/server/util/VersionCompatibilityIssue.java |   24 ++++++++++++++++--------
 1 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/opends/src/server/org/opends/server/util/VersionCompatibilityIssue.java b/opends/src/server/org/opends/server/util/VersionCompatibilityIssue.java
index ae323cc..658f420 100644
--- a/opends/src/server/org/opends/server/util/VersionCompatibilityIssue.java
+++ b/opends/src/server/org/opends/server/util/VersionCompatibilityIssue.java
@@ -44,7 +44,7 @@
  * Record for version compatibility issues (also known as 'flag days') which
  * are events associated with particular builds or builds between which upgrade
  * or reversion may required additional steps, notification of issues, or
- * be prohibitted altogether.
+ * be prohibited altogether.
  */
 @org.opends.server.types.PublicAPI(
      stability=org.opends.server.types.StabilityLevel.VOLATILE,
@@ -179,7 +179,7 @@
      * following a reversion.  There might be situations where the admin
      * needs to perform some actions before the server restarts (such as
      * the database format being incompatible and the data needing an
-     * export followed by a reimport).  This effect need not be included
+     * export followed by a re-import).  This effect need not be included
      * with <code>UPGRADE_DATA_EXPORT_AND_REIMPORT_REQUIRED</code> and
      * <code>REVERSION_DATA_EXPORT_AND_REIMPORT_REQUIRED</code> as this
      * is assumed.
@@ -201,12 +201,12 @@
   //          a unique ID.
   //
   //          A single issue may be apply to multiple branches of the
-  //          codebase.  For instance a single event might cause a flag
+  //          code-base.  For instance a single event might cause a flag
   //          day between upgrade/reversions from 1.0 to 2.0 as well as
   //          upgrading from 1.0 to 1.1.  Therefore you must make sure
   //          that causes that appear in multiple branches have the same
   //          ID.  Also, IDs should be unique among all causes in the
-  //          codebase.
+  //          code-base.
   //
   // STEP 3:  [scroll down]
   //
@@ -218,6 +218,17 @@
    */
   public enum Cause {
     /**
+     * Incompatible changes in DN normalization. This causes dn2id and
+     * RDN / DN syntax based attribute indexes to be invalidated.
+     */
+    DN_NORMALIZATION_CHANGE_1(
+        7, // Unique ID.  See javadoc for more information.
+        INFO_3873_UPGRADE.get(),
+        INFO_3873_REVERSION.get(),
+        Effect.REVERSION_DATA_EXPORT_AND_REIMPORT_REQUIRED,
+        Effect.UPGRADE_DATA_EXPORT_AND_REIMPORT_REQUIRED),
+
+    /**
      * Incompatible changes in the backend configuration (the db directory
      * attribute has been modified).
      */
@@ -448,7 +459,7 @@
   //***************************************************
 
   static {
-    //
+    register(Cause.DN_NORMALIZATION_CHANGE_1, new BuildVersion(1, 0, 0, 3873));
     register(Cause.BACKEND_CONFIGURATION_CHANGE_1,
         new BuildVersion(1, 0, 0, 3708));
     register(Cause.REPLICATION_SECURITY_CHANGE_1,
@@ -501,9 +512,6 @@
     for (VersionCompatibilityIssue evt : VERSION_COMPATIBILITY_ISSUES) {
       if (!excludeIds.contains(evt.getCause().getId())) {
         boolean isUpgrade = neu.compareTo(current) >= 0;
-        BuildVersion newVersion = new BuildVersion(neu.getMajorVersion(),
-            neu.getMinorVersion(), neu.getPointVersion(),
-            neu.getRevisionNumber());
         BuildVersion currentVersion = new BuildVersion(
             current.getMajorVersion(), current.getMinorVersion(),
             current.getPointVersion(), current.getRevisionNumber());

--
Gitblit v1.10.0