org.apache.qpid.server.store.berkeleydb.upgrade

Class UpgradeFrom5To6

java.lang.Object

org.apache.qpid.server.store.berkeleydb.upgrade.AbstractStoreUpgrade

org.apache.qpid.server.store.berkeleydb.upgrade.UpgradeFrom5To6

All Implemented Interfaces:

StoreUpgrade

public class UpgradeFrom5To6
extends AbstractStoreUpgrade

Constructor Summary

Constructors

Constructor and Description
UpgradeFrom5To6()

Method Summary

Modifier and Type	Method and Description
void	performUpgrade(com.sleepycat.je.Environment environment, UpgradeInteractionHandler handler, ConfiguredObject<?> parent) Upgrades from a v5 database to a v6 database v6 is the first "new style" schema where we don't version every table, and the upgrade is re-runnable Change in this version: Message content is moved from the database messageContentDb_v5 to MESSAGE_CONTENT.

Methods inherited from class org.apache.qpid.server.store.berkeleydb.upgrade.AbstractStoreUpgrade

reportFinished, reportStarting

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

UpgradeFrom5To6

public UpgradeFrom5To6()

Method Detail

performUpgrade

public void performUpgrade(com.sleepycat.je.Environment environment,
                           UpgradeInteractionHandler handler,
                           ConfiguredObject<?> parent)

Upgrades from a v5 database to a v6 database v6 is the first "new style" schema where we don't version every table, and the upgrade is re-runnable Change in this version: Message content is moved from the database messageContentDb_v5 to MESSAGE_CONTENT. The structure of the database changes from ( message-id: long, chunk-id: int ) -> ( size: int, byte[] data ) to ( message-id: long) -> ( byte[] data ) That is we keep only one record per message, which contains all the message content Queue, Exchange, Bindings entries are stored now as configurable objects in "CONFIGURED_OBJECTS" table.