[
https://issues.apache.org/jira/browse/QPID-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968178#comment-13968178
]
ASF subversion and git services commented on QPID-5685:
-------------------------------------------------------
Commit 1587165 from [email protected] in branch 'qpid/trunk'
[ https://svn.apache.org/r1587165 ]
QPID-5685: Store configuration version as an attribute of virtualhost within
configuration store rather than within separate database/table
* ConfiguredObjectRecordHandler begin/end methods no longer take/return config
version
* DefaultUpgraderProvider uses the virtualhost record for the config version
only and uses this to trigger
the correct upgrade. Note this record is *not* recovered (yet).
* BDB/SQL Upgraders migrate the config version from database/table to be the
modelVersion attribute of a virtualhost entry.
* BDB Upgrader tests (7 to 8).
> Store config version as an attribute of virtualhost within configuration store
> ------------------------------------------------------------------------------
>
> Key: QPID-5685
> URL: https://issues.apache.org/jira/browse/QPID-5685
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Attachments:
> 0001-QPID-5685-Store-configuration-version-as-an-attribut.patch
>
>
> Currently the Derby and BDB stores store the configuration version (the
> version number that describes the format of the configuration objects) within
> a separate table/database.
> It has been decided to the move this configuration version information into
> the configuration store itself. It will reside as a modelVersion attribute
> on a new VirtualHost record.
> This commit will change the structure of the stores to eliminate the
> config_version table/database. Store upgraders produce the virtualhost
> record, populating the version from version number in table, prepending "0.".
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
