orc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Gates <alanfga...@gmail.com>
Subject Re: [VOTE] Should we release ORC-1.3.1rc0?
Date Thu, 02 Feb 2017 19:29:41 GMT
+1.  Checked the signatures, did a build on centos 7.  

Alan.

> On Feb 1, 2017, at 1:26 PM, Owen O'Malley <omalley@apache.org> wrote:
> 
> I forgot to include the links:
> 
> tarball: http://home.apache.org/~omalley/orc-1.3.1rc0/
> tag: https://github.com/apache/orc/releases/tag/release-1.3.1rc0
> 
> .. Owen
> 
> On Wed, Feb 1, 2017 at 11:15 AM, Alan Gates <alanfgates@gmail.com> wrote:
> 
>> I'm +1 to releasing, as I believe Hive 2.next will need ORC-134 and
>> ORC-138.  I don't have enough information to make a call on the risk vs
>> reward for ORC-135.
>> 
>> Alan.
>> 
>>> On Jan 31, 2017, at 9:06 AM, Owen O'Malley <omalley@apache.org> wrote:
>>> 
>>> All,
>>>  We have a couple of bug fixes that have gone in and I think we should
>>> make a release.
>>> 
>>> Fixes:
>>> * ORC-134 DecimalColumnStatistics throws NPE when all column values are
>>> null.
>>> * ORC-100 Make findbugs a mandatory part of the build and fixed all of
>> the
>>> current warnings.
>>> * ORC-138 Fix forward port of HIVE-15335 that messed up schema evolution
>>> for decimal.
>>> 
>>> The other one that is pending is ORC-135 (predicate pushdown for
>> timestamp
>>> is sensitive to
>>> changing timezones) is important, but I want to be really careful with
>> that
>>> one since it is a
>>> larger change. I'm in the middle of reviewing that one and that one is a
>>> lot riskier change.
>>> 
>>> .. Owen
>> 
>> 


Mime
View raw message