+1
-- Lefty
On Wed, May 27, 2015 at 3:21 PM, Alexander Pivovarov
wrote:
> +1
> On May 27, 2015 10:45 AM, "Vikram Dixit K" wrote:
>
> > +1 for all the reasons outlined.
> >
> > On Tue, May 26, 2015 at 6:13 PM, Thejas Nair
> > wrote:
> > > +1
> > > - This is great for users who want to take lon
+1
On May 27, 2015 10:45 AM, "Vikram Dixit K" wrote:
> +1 for all the reasons outlined.
>
> On Tue, May 26, 2015 at 6:13 PM, Thejas Nair
> wrote:
> > +1
> > - This is great for users who want to take longer to upgrade from
> > hadoop-1 and care mainly for bug fixes and incremental features,
> >
+1 for all the reasons outlined.
On Tue, May 26, 2015 at 6:13 PM, Thejas Nair wrote:
> +1
> - This is great for users who want to take longer to upgrade from
> hadoop-1 and care mainly for bug fixes and incremental features,
> rather than radical new features.
> - The ability to release initial 2
+1
- This is great for users who want to take longer to upgrade from
hadoop-1 and care mainly for bug fixes and incremental features,
rather than radical new features.
- The ability to release initial 2.x releases marked as alpha/beta
also helps to get users to try it out, and also lets them choose
+1
I hope that important bugfixes (and functionality) will be backported from
trunk to branch-1 for a reasonable amount of time given that many people will
continue to rely on branch-1.
Thanks,
chris
On Tuesday, May 26, 2015 1:45 PM, Gopal Vijayaraghavan
wrote:
+1
This would pro
+1
This would protect those who might not want to lose workflow features from
the stable
releases for the coming year.
I¹m not looking forward to a branch merge tearing out the hive CLI client
away in a
single chop.
Having a master branch where we can plan for the future is essential and
this is
+1.
I think this will help a lot in having a clean way to experiment with new
features.
‹Vaibhav
On 5/26/15, 12:29 PM, "Sergey Shelukhin" wrote:
>+1.
>I want to clarify about being not production ready though. That shouldn¹t
>mean known shortage of functionality (other than the deprecated part
I'm +1 too. I think it is important to allow the Hive development community
to move forward with these big features while supporting users who want a
more conservative set of features and more backwards compatibility.
.. Owen
On Tue, May 26, 2015 at 12:29 PM, Sergey Shelukhin
wrote:
> +1.
> I w
+1.
I want to clarify about being not production ready though. That shouldn’t
mean known shortage of functionality (other than the deprecated parts like
hadoop-1), imho, just the fact that they are recent with big features
enabled. They should be production ready modulo the higher expected bug
coun
We have discussed this for several weeks now. Some concerns have been
raised which I have tried to address. I think it is time to vote on it
as our release plan. To be specific, I propose:
Hive makes a branch-1 from the current master. This would be used for
1.3 and future 1.x releases. T
10 matches
Mail list logo
