>>> I would get the Database Format and Configuration out of the equation. >>> It's >>> up to us to provide tools to migrate from one format to the other. Don't >>> get >>> me wrong : when I say that configuration is out of the equation, I mean >>> that >>> the configuration can change, not its format (ie switching from XML to >>> DIT >>> is possible between to major releases, not between two minor releases). >>> >>> >> Will this be transparent to the user? Meaning can he just upgrade the >> software and the migration will occur without any change in their >> workflow, >> or anything noticeable in performance, wait time on startup? More >> specifically: >> >> (1) Does the user have to run a tool to migrate from one version to the >> next >> ? > > Definitively, yes.
I think the database format must be stable between micro (bugfix) and minor (feature enhancement) releases. For major releases it is acceptable to change the format and to provide a migration tool. Please keep in mind that the current JDBM format is not final yet. We introduced the RDN index for fast moddn operation, but still have the oneLevel, subLevel, and alias indices that are not updated in O(1). Kind Regards, Stefan
