On Wed, Jul 5, 2017 at 12:33 PM, Edward Capriolo <edlinuxg...@gmail.com>
wrote:

>
> I hate to draw in something else but I feel it is related:
>
> 8 December 2016 : release 2.1.1 available
> 07 April 2017 : release 1.2.2 available
> hive-dev [DISCUSS] Supporting Hadoop-1 and experimental features
> hive-dev Re: release chaos?
>
> I have been vocal about not liking certain branching strategies and
> proposals that take us away from releasable trunk. We have steadily headed
> in a direction where we are pulling things out of hive, and we are not able
> to turn out releases. We even had a thread "release chaos" talking about
> our 5 active branches (with friends I say "jumped the shark"). Pulling out
> the metastore is only going to make this worse. I do not even see the model
> as successful. You may say it is great that calcite lets people share our
> sql dialect or the ORC TLP has 5 committers, but if Hive can not get a
> release out the door I do not see us optimizing for the proper thing.
>

I don’t see the relationship between these issues.  I agree Hive is not
releasing frequently enough.  I agree that breaking out the metastore won’t
fix that.  It isn’t intended to fix that.  But as stated elsewhere in this
thread there are ways to make sure it won’t make it any worse either.

Alan.

Reply via email to