Christopher wrote:
So,
instance.volumes replaces instance.dfs.uri and instance.dfs.dir in 1.6.
But, what's our long-term plan for these? I ask, because we still have
internal code that uses instance.dfs.uri to resolve relative paths.
Should we force these to be re-written at some point (maybe on upgrade to
1.7)? Should we continue to support the deprecated properties indefinitely
and continue the lazy re-write-on-compact? Do we transition by requiring
instance.volumes to specify the volumes, and only use the old properties to
resolve relative paths?
+1 Making a utility that does the upgrade would be so nice over trying
to get everything else right ourselves. 2.0 sounds like a good time to
do it (since we deprecated the properties in 1.6.0)
My personal view is that we should provide an upgrade-prep/check tool prior
to upgrade to 2.0, which checks and/or re-writes paths and verifies that
instance.volumes is set.
Does anybody have a different opinion on this?
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
