I think you're right, that there's no risk to wire compatibility in this
issue, and the data version wouldn't change in any way, so rollback should
be fine, too. The discussion here is simply a discussion of when/how to
accelerate a metadata upgrade that was already in place in 1.6.0, but did
so gradually in 1.6.0. The question at the heart of the matter here is:
when can we safely write code that no longer has to have special
considerations for relative paths written from older versions?
Christopher L Tubbs II
On Wed, Jul 23, 2014 at 9:17 PM, Mike Drob <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB