[jira] [Resolved] (HADOOP-12679) while performing the simple queries on s3 table through hive ,got exception:-Error: java.io.IOException: java.lang.reflect.InvocationTargetException

[ https://issues.apache.org/jira/browse/HADOOP-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-12679. - Resolution: Invalid {{: Class org.apache.hadoop.fs.s3native.NativeS3FileSystem not found

Build failed in Jenkins: Hadoop-common-trunk-Java8 #856

See Changes: [ozawa] YARN-4234. addendum patch to remove unnecessary file. Contributed by -- [...truncated 5818 lines...] Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

Jenkins build is back to normal : Hadoop-Common-trunk #2152

See

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

My 2c is that we should have monotonicity in releases. That way no "upgrade" is a regression. On Wed, Dec 23, 2015 at 10:00 PM, Tsuyoshi Ozawa wrote: > Hi Vinod, > > thank you for the clarification. > > > - Pull these 16 tickets into 2.7.2 and roll a new RC > > > What do people think? Do folks

[jira] [Resolved] (HADOOP-12676) Inconsistent assumptions of the default keytab file of Kerberos

[ https://issues.apache.org/jira/browse/HADOOP-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyin Xu resolved HADOOP-12676. - Resolution: Invalid > Inconsistent assumptions of the default keytab file of Kerberos >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

Thanks Vinod for starting the discussion. I'm +1 for cherry-picking these issues to 2.7.2. As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2, they can hit the issues. I'm thinking we should reduce the regressions as possible. Regards, Akira On 12/25/15 01:56, Andrew Wang wrote: My