[
https://issues.apache.org/jira/browse/OAK-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-3739.
---------------------------------
Resolution: Fixed
trunk: http://svn.apache.org/r1723333
1.2: http://svn.apache.org/r1723335
1.0: http://svn.apache.org/r1723337
> RDBDocumentStore: allow schema evolution part 1: check for required columns,
> log unexpected new columns
> -------------------------------------------------------------------------------------------------------
>
> Key: OAK-3739
> URL: https://issues.apache.org/jira/browse/OAK-3739
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: rdbmk
> Affects Versions: 1.2.9, 1.0.25, 1.3.13
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 1.0.26, 1.2.10, 1.3.14
>
>
> In the future, we may have to add new table columns (for instance, see
> OAK-3730).
> We can somewhat decouple database changes from code changes by only using new
> columns when they are present.
> However, we need to make sure that once the columns have been added and the
> system has started to use them, no older code writes to the DB (potentially
> causing inconsistencies because of not updating these columns).
> To prevent this, code could check that it understands all columns it finds on
> startup. If there are unknown columns, it would need to abort and log an
> error that explains the compatibility issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
