accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dlmarion <>
Subject RE: Planning for (eventual) removal of instance.dfs.{uri,dir}
Date Thu, 11 Dec 2014 01:59:29 GMT
We should schedule a bunch of deprecated things for removal in 2.0 to ease maintenance. Do
we have a way to validate the site.xml and zookeeper settings before startup and fail with
appropriate error message.

<div>-------- Original message --------</div><div>From: Christopher <>
</div><div>Date:12/10/2014  8:44 PM  (GMT-05:00) </div><div>To: Accumulo
Dev List <> </div><div>Cc:  </div><div>Subject:
Planning for (eventual) removal of instance.dfs.{uri,dir} </div><div>

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?

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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message