Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Won't Fix
-
1.7.2, 1.7.3, 1.8.0, 1.8.1
-
None
-
None
-
None
Description
The createReplicationTable method in the MetadataTableUtil used to create the replication table when upgrading from 1.6 and calls the default volume chooser to get a location. The problem is that at that point the replication table does not exist and the PerTableVolumeChooser and the PreferredTableVolumeChooser classes will call the getTableConfiguration with the supplied table id which will return null. Subsequently those volume choosers will throw a NullPointerException and the upgrade will fail. Both of these volume choosers should instead use the fallbacks instead of failing.