[jira] [Created] (HADOOP-10978) HADOOP_IDENT_STRING is overriden in hadoop-env.sh

[Mathias Herberts (JIRA)]

Mathias Herberts created HADOOP-10978:
-

 Summary: HADOOP_IDENT_STRING is overriden in hadoop-env.sh
 Key: HADOOP-10978
 URL: https://issues.apache.org/jira/browse/HADOOP-10978
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Mathias Herberts
Priority: Minor


hadoop-env.sh forces HADOOP_IDENT_STRING to $USER possibly overriding a 
previously set value.

Instead hadoop-env.sh should set HADOOP_IDENT_STRING to:

export HADOOP_IDENT_STRING=${HADOOP_IDENT_STRING:-$USER}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HADOOP-10979) [post-HADOOP-9902] Auto-entries in hadoop_usage

[Allen Wittenauer (JIRA)]

Allen Wittenauer created HADOOP-10979:
-

 Summary: [post-HADOOP-9902] Auto-entries in hadoop_usage
 Key: HADOOP-10979
 URL: https://issues.apache.org/jira/browse/HADOOP-10979
 Project: Hadoop Common
  Issue Type: Improvement
Reporter: Allen Wittenauer
Priority: Minor


It would make adding common options to hadoop_usage output easier if some 
entries were auto-populated.  This is similar to what happens in FsShell and 
other parts of the Java code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Build failed in Jenkins: Hadoop-Common-0.23-Build #1046

[Apache Jenkins Server]

See 

--
[...truncated 8263 lines...]
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.555 sec
Running org.apache.hadoop.util.TestJarFinder
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.813 sec
Running org.apache.hadoop.util.TestProtoUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 sec
Running org.apache.hadoop.util.TestShutdownHookManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.154 sec
Running org.apache.hadoop.util.TestPureJavaCrc32
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.297 sec
Running org.apache.hadoop.http.TestPathFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.78 sec
Running org.apache.hadoop.http.lib.TestStaticUserWebFilter
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.535 sec
Running org.apache.hadoop.http.TestHttpServer
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.695 sec
Running org.apache.hadoop.http.TestHttpRequestLogAppender
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.hadoop.http.TestHttpRequestLog
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.166 sec
Running org.apache.hadoop.http.TestHttpServerLifecycle
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.321 sec
Running org.apache.hadoop.http.TestServletFilter
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.05 sec
Running org.apache.hadoop.http.TestHtmlQuoting
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.293 sec
Running org.apache.hadoop.http.TestHttpServerWebapps
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.461 sec
Running org.apache.hadoop.http.TestGlobalFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.775 sec
Running org.apache.hadoop.jmx.TestJMXJsonServlet
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.873 sec
Running org.apache.hadoop.io.TestMD5Hash
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.161 sec
Running org.apache.hadoop.io.serializer.TestSerializationFactory
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.301 sec
Running org.apache.hadoop.io.serializer.avro.TestAvroSerialization
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.614 sec
Running org.apache.hadoop.io.serializer.TestWritableSerialization
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.373 sec
Running org.apache.hadoop.io.TestSecureIOUtils
Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.617 sec
Running org.apache.hadoop.io.TestDataByteBuffers
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.662 sec
Running org.apache.hadoop.io.compress.TestCompressorDecompressor
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.301 sec
Running org.apache.hadoop.io.compress.TestCodec
Tests run: 23, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 59.097 sec <<< 
FAILURE!
testSnappyCodec(org.apache.hadoop.io.compress.TestCodec)  Time elapsed: 13 sec  
<<< FAILURE!
java.lang.AssertionError: Snappy native available but Hadoop native not
at org.junit.Assert.fail(Assert.java:91)
at 
org.apache.hadoop.io.compress.TestCodec.__CLR3_0_2v4ia4819ya(TestCodec.java:132)
at 
org.apache.hadoop.io.compress.TestCodec.testSnappyCodec(TestCodec.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at 
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.j

Re: Apache Hadoop 2.5.0 published tarballs are missing some txt files

[Andre Kelpe]

Are you guys aware that the 2.5.0 tarballs are already on the mirrors?
http://mirror.derwebwolf.net/apache/hadoop/common/hadoop-2.5.0/

- André


On Mon, Aug 18, 2014 at 9:42 PM, Karthik Kambatla 
wrote:

> Hi devs
>
> Tsuyoshi just brought it to my notice that the published tarballs don't
> have LICENSE, NOTICE and README at the top-level. Instead, they are only
> under common, hdfs, etc.
>
> Now that we have already announced the release and the jars/functionality
> doesn't change, I propose we just update the tarballs with ones that
> includes those files? I just untar-ed the published tarballs and copied
> LICENSE, NOTICE and README from under common to the top directory and
> tar-ed them back again.
>
> The updated tarballs are at: http://people.apache.org/~kasha/hadoop-2.5.0/
> . Can someone please verify the signatures?
>
> If you would prefer an alternate action, please suggest.
>
> Thanks
> Karthik
>
> PS: HADOOP-10956 should include the fix for these files also.
>



-- 
André Kelpe
an...@concurrentinc.com
http://concurrentinc.com

[jira] [Created] (HADOOP-10980) TestActiveStandbyElector fails occasionally in trunk

[Ted Yu (JIRA)]

Ted Yu created HADOOP-10980:
---

 Summary: TestActiveStandbyElector fails occasionally in trunk
 Key: HADOOP-10980
 URL: https://issues.apache.org/jira/browse/HADOOP-10980
 Project: Hadoop Common
  Issue Type: Test
Reporter: Ted Yu
Priority: Minor


>From https://builds.apache.org/job/Hadoop-Common-trunk/1211/consoleFull :
{code}
Running org.apache.hadoop.ha.TestActiveStandbyElector
Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.7 sec <<< 
FAILURE! - in org.apache.hadoop.ha.TestActiveStandbyElector
testWithoutZKServer(org.apache.hadoop.ha.TestActiveStandbyElector)  Time 
elapsed: 0.051 sec  <<< FAILURE!
java.lang.AssertionError: Did not throw zookeeper connection loss exceptions!
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.hadoop.ha.TestActiveStandbyElector.testWithoutZKServer(TestActiveStandbyElector.java:722)
{code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Apache Hadoop 2.5.0 published tarballs are missing some txt files

[Arun Murthy]

I suggest we do a 2.5.1 (with potentially other bug fixes) rather than fix
existing tarballs.

thanks,
Arun


On Mon, Aug 18, 2014 at 12:42 PM, Karthik Kambatla 
wrote:

> Hi devs
>
> Tsuyoshi just brought it to my notice that the published tarballs don't
> have LICENSE, NOTICE and README at the top-level. Instead, they are only
> under common, hdfs, etc.
>
> Now that we have already announced the release and the jars/functionality
> doesn't change, I propose we just update the tarballs with ones that
> includes those files? I just untar-ed the published tarballs and copied
> LICENSE, NOTICE and README from under common to the top directory and
> tar-ed them back again.
>
> The updated tarballs are at: http://people.apache.org/~kasha/hadoop-2.5.0/
> . Can someone please verify the signatures?
>
> If you would prefer an alternate action, please suggest.
>
> Thanks
> Karthik
>
> PS: HADOOP-10956 should include the fix for these files also.
>



-- 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Dropping support for JDK6 in Apache Hadoop

[Arun C Murthy]

[Apologies for the wide distribution.]

Dear HBase/Hive/Pig/Oozie communities,

 We, over at Hadoop are considering dropping support for JDK6 this year. 

 As you maybe aware we just released hadoop-2.5.0 and are now considering 
making the next release i.e. hadoop-2.6.0 the *last* release of Apache Hadoop 
which supports JDK6. This means, from hadoop-2.7.0 onwards we will not support 
JDK6 anymore and we *may* start relying on JDK7-specific apis.

 Now, the above releases a proposal and we do not want to pull the trigger 
without talking to projects downstream - hence the request for you feedback.

 Please feel free to forward this to other communities you might deem to be at 
risk from this too.

thanks,
Arun


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Dropping support for JDK6 in Apache Hadoop

[Konstantin Boudnik]

While it sounds like a topic for a different discussion (or list@), do you
think it would be too crazy to skip JDK7 completely and just go to JDK8
directly? I think downstream components like HBase, Spark and so on would be a
huge driving factor to make the same change in Hadoop and other parts of the
ecosystem.

Thoughts?
  Cos
   
On Tue, Aug 19, 2014 at 11:23AM, Devaraj Das wrote:
> I think we are good on HBase side, at least on the 1.x+ branches. We
> are dropping support for 1.6 from HBase-1.0 onwards.
> 
> On Tue, Aug 19, 2014 at 10:52 AM, Arun C Murthy  wrote:
> > [Apologies for the wide distribution.]
> >
> > Dear HBase/Hive/Pig/Oozie communities,
> >
> >  We, over at Hadoop are considering dropping support for JDK6 this year.
> >
> >  As you maybe aware we just released hadoop-2.5.0 and are now considering 
> > making the next release i.e. hadoop-2.6.0 the *last* release of Apache 
> > Hadoop which supports JDK6. This means, from hadoop-2.7.0 onwards we will 
> > not support JDK6 anymore and we *may* start relying on JDK7-specific apis.
> >
> >  Now, the above releases a proposal and we do not want to pull the trigger 
> > without talking to projects downstream - hence the request for you feedback.
> >
> >  Please feel free to forward this to other communities you might deem to be 
> > at risk from this too.
> >
> > thanks,
> > Arun
> >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender immediately
> > and delete it from your system. Thank You.
> 
> -- 
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to 
> which it is addressed and may contain information that is confidential, 
> privileged and exempt from disclosure under applicable law. If the reader 
> of this message is not the intended recipient, you are hereby notified that 
> any printing, copying, dissemination, distribution, disclosure or 
> forwarding of this communication is strictly prohibited. If you have 
> received this communication in error, please contact the sender immediately 
> and delete it from your system. Thank You.

Re: Dropping support for JDK6 in Apache Hadoop

[Steve Loughran]

On 19 August 2014 19:44, Konstantin Boudnik  wrote:

> While it sounds like a topic for a different discussion (or list@), do you
> think it would be too crazy to skip JDK7 completely and just go to JDK8
> directly?


The trouble with that as nobody who provides commercial big-data stacks is
going to to commit to  java 8+ only in 2014, or the things downstream.

Switching to Java 7 now not only gives us a start to that by getting off
all pretence of Java 6 support, it frees up those QE teams from having to
look at Java 7.

While the Java 8 language changes are the really compelling ones, mandating
it right now would only postpone any switch to Java > 6.

Otherwise, I'm +1 for any switch to Java 7, and in the slider project we're
ready for it as soon as the switch can happen.

-steve




> I think downstream components like HBase, Spark and so on would be a
> huge driving factor to make the same change in Hadoop and other parts of
> the
> ecosystem.
>
> Thoughts?
>   Cos
>
> On Tue, Aug 19, 2014 at 11:23AM, Devaraj Das wrote:
> > I think we are good on HBase side, at least on the 1.x+ branches. We
> > are dropping support for 1.6 from HBase-1.0 onwards.
> >
> > On Tue, Aug 19, 2014 at 10:52 AM, Arun C Murthy 
> wrote:
> > > [Apologies for the wide distribution.]
> > >
> > > Dear HBase/Hive/Pig/Oozie communities,
> > >
> > >  We, over at Hadoop are considering dropping support for JDK6 this
> year.
> > >
> > >  As you maybe aware we just released hadoop-2.5.0 and are now
> considering making the next release i.e. hadoop-2.6.0 the *last* release of
> Apache Hadoop which supports JDK6. This means, from hadoop-2.7.0 onwards we
> will not support JDK6 anymore and we *may* start relying on JDK7-specific
> apis.
> > >
> > >  Now, the above releases a proposal and we do not want to pull the
> trigger without talking to projects downstream - hence the request for you
> feedback.
> > >
> > >  Please feel free to forward this to other communities you might deem
> to be at risk from this too.
> > >
> > > thanks,
> > > Arun
> > >
> > >
> > > --
> > > CONFIDENTIALITY NOTICE
> > > NOTICE: This message is intended for the use of the individual or
> entity to
> > > which it is addressed and may contain information that is confidential,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notified
> that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> immediately
> > > and delete it from your system. Thank You.
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Apache Hadoop 2.5.0 published tarballs are missing some txt files

[Steve Loughran]

On 19 August 2014 18:35, Arun Murthy  wrote:

> I suggest we do a 2.5.1 (with potentially other bug fixes) rather than fix
> existing tarballs.
>


do we already have enough last-minute fixes to trigger a rerelease? With
all the testing that entails?

A simple 2.5.1 rebuild with the same hadoop source tree would be a lot
easier to push out


>
> thanks,
> Arun
>
>
> On Mon, Aug 18, 2014 at 12:42 PM, Karthik Kambatla 
> wrote:
>
> > Hi devs
> >
> > Tsuyoshi just brought it to my notice that the published tarballs don't
> > have LICENSE, NOTICE and README at the top-level. Instead, they are only
> > under common, hdfs, etc.
> >
> > Now that we have already announced the release and the jars/functionality
> > doesn't change, I propose we just update the tarballs with ones that
> > includes those files? I just untar-ed the published tarballs and copied
> > LICENSE, NOTICE and README from under common to the top directory and
> > tar-ed them back again.
> >
> > The updated tarballs are at:
> http://people.apache.org/~kasha/hadoop-2.5.0/
> > . Can someone please verify the signatures?
> >
> > If you would prefer an alternate action, please suggest.
> >
> > Thanks
> > Karthik
> >
> > PS: HADOOP-10956 should include the fix for these files also.
> >
>
>
>
> --
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Dropping support for JDK6 in Apache Hadoop

[Roman Shaposhnik]

FWIW: in Bigtop we've made the switch to JDK7 for the Bigtop
0.8.0 release across the board. No major issues so far.

Thanks,
Roman.

On Tue, Aug 19, 2014 at 10:52 AM, Arun C Murthy  wrote:
> [Apologies for the wide distribution.]
>
> Dear HBase/Hive/Pig/Oozie communities,
>
>  We, over at Hadoop are considering dropping support for JDK6 this year.
>
>  As you maybe aware we just released hadoop-2.5.0 and are now considering 
> making the next release i.e. hadoop-2.6.0 the *last* release of Apache Hadoop 
> which supports JDK6. This means, from hadoop-2.7.0 onwards we will not 
> support JDK6 anymore and we *may* start relying on JDK7-specific apis.
>
>  Now, the above releases a proposal and we do not want to pull the trigger 
> without talking to projects downstream - hence the request for you feedback.
>
>  Please feel free to forward this to other communities you might deem to be 
> at risk from this too.
>
> thanks,
> Arun
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

[jira] [Resolved] (HADOOP-10951) Make org.apache.hadoop.security.Groups public

[Hitesh Shah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HADOOP-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hitesh Shah resolved HADOOP-10951.
--

Resolution: Not a Problem

> Make org.apache.hadoop.security.Groups public
> -
>
> Key: HADOOP-10951
> URL: https://issues.apache.org/jira/browse/HADOOP-10951
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Hitesh Shah
>
> This class seems like useful functionality for most developers building yarn 
> applications with respect to application acls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Dropping support for JDK6 in Apache Hadoop

[Matt Foley]

Yes, in terms of forward compatibility, my company has been certifying the
current Hadoop-related stack on JDK7 (both Oracle and OpenJDK) for some
time.  No problems there, in our experience.

For stopping supporting JDK6 in the near future, and enabling JDK7 feature
usage, +1.

--Matt


On Tue, Aug 19, 2014 at 2:37 PM, Roman Shaposhnik  wrote:

> FWIW: in Bigtop we've made the switch to JDK7 for the Bigtop
> 0.8.0 release across the board. No major issues so far.
>
> Thanks,
> Roman.
>
> On Tue, Aug 19, 2014 at 10:52 AM, Arun C Murthy 
> wrote:
> > [Apologies for the wide distribution.]
> >
> > Dear HBase/Hive/Pig/Oozie communities,
> >
> >  We, over at Hadoop are considering dropping support for JDK6 this year.
> >
> >  As you maybe aware we just released hadoop-2.5.0 and are now
> considering making the next release i.e. hadoop-2.6.0 the *last* release of
> Apache Hadoop which supports JDK6. This means, from hadoop-2.7.0 onwards we
> will not support JDK6 anymore and we *may* start relying on JDK7-specific
> apis.
> >
> >  Now, the above releases a proposal and we do not want to pull the
> trigger without talking to projects downstream - hence the request for you
> feedback.
> >
> >  Please feel free to forward this to other communities you might deem to
> be at risk from this too.
> >
> > thanks,
> > Arun
> >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[jira] [Created] (HADOOP-10981) native client: parse Hadoop permission strings

[Colin Patrick McCabe (JIRA)]

Colin Patrick McCabe created HADOOP-10981:
-

 Summary: native client: parse Hadoop permission strings
 Key: HADOOP-10981
 URL: https://issues.apache.org/jira/browse/HADOOP-10981
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: native
Affects Versions: HADOOP-10388
Reporter: Colin Patrick McCabe


The native client should parse Hadoop permission strings like 
PermissionParser.java does.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HADOOP-10984) Add hostname to filename of KMS log

[Andrew Wang (JIRA)]

Andrew Wang created HADOOP-10984:


 Summary: Add hostname to filename of KMS log
 Key: HADOOP-10984
 URL: https://issues.apache.org/jira/browse/HADOOP-10984
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Andrew Wang
Assignee: Alejandro Abdelnur


It'd be nice if, rather than being named "kms.log", the log filename included 
the hostname, e.g. "kms-${hostname}.log".



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HADOOP-10985) native client: split ndfs.c into meta, file, util, and permission

[Colin Patrick McCabe (JIRA)]

Colin Patrick McCabe created HADOOP-10985:
-

 Summary: native client: split ndfs.c into meta, file, util, and 
permission
 Key: HADOOP-10985
 URL: https://issues.apache.org/jira/browse/HADOOP-10985
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: native
Affects Versions: HADOOP-10388
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe


Split ndfs.c into meta.c, file.c, util.c, and permission.c.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Apache Hadoop 2.5.0 published tarballs are missing some txt files

[Alejandro Abdelnur]

agree with Steve, lets do a 2.5.1 just with those txt files.


On Tue, Aug 19, 2014 at 2:29 PM, Steve Loughran 
wrote:

> On 19 August 2014 18:35, Arun Murthy  wrote:
>
> > I suggest we do a 2.5.1 (with potentially other bug fixes) rather than
> fix
> > existing tarballs.
> >
>
>
> do we already have enough last-minute fixes to trigger a rerelease? With
> all the testing that entails?
>
> A simple 2.5.1 rebuild with the same hadoop source tree would be a lot
> easier to push out
>
>
> >
> > thanks,
> > Arun
> >
> >
> > On Mon, Aug 18, 2014 at 12:42 PM, Karthik Kambatla 
> > wrote:
> >
> > > Hi devs
> > >
> > > Tsuyoshi just brought it to my notice that the published tarballs don't
> > > have LICENSE, NOTICE and README at the top-level. Instead, they are
> only
> > > under common, hdfs, etc.
> > >
> > > Now that we have already announced the release and the
> jars/functionality
> > > doesn't change, I propose we just update the tarballs with ones that
> > > includes those files? I just untar-ed the published tarballs and copied
> > > LICENSE, NOTICE and README from under common to the top directory and
> > > tar-ed them back again.
> > >
> > > The updated tarballs are at:
> > http://people.apache.org/~kasha/hadoop-2.5.0/
> > > . Can someone please verify the signatures?
> > >
> > > If you would prefer an alternate action, please suggest.
> > >
> > > Thanks
> > > Karthik
> > >
> > > PS: HADOOP-10956 should include the fix for these files also.
> > >
> >
> >
> >
> > --
> >
> > --
> > Arun C. Murthy
> > Hortonworks Inc.
> > http://hortonworks.com/
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>



-- 
Alejandro