Re: 2.7 status

> >> vino...@hortonworks.com> wrote: > >>>>> > >>>>>> > >>>>>> The 2.7 blocker JIRA went down and going back up again, we will need > >> to converge. > >>>>>> > >>>>>> Unless

Re: 2.7 status

i < >> vino...@hortonworks.com> wrote: >>>>> >>>>>> >>>>>> The 2.7 blocker JIRA went down and going back up again, we will need >> to converge. >>>>>> >>>>>> Unless I see o

Re: 2.7 status

at in the interest of convergence. > >>>> > >>>> Thoughts welcome! > >>>> > >>>> Thanks, > >>>> +Vinod > >>>> > >>>> On Mar 1, 2015, at 11:58 AM, Arun Murthy wrote: > >>&g

Re: 2.7 status

nod Kumar Vavilapalli > Sent: Monday, March 30, 2015 3:35 PM > To: mapreduce-...@hadoop.apache.org > Cc: yarn-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Hadoop Common > Subject: Re: 2.7 status > > This is the filter I am using: > https://issues.apache.org/jira/issues/?

Re: 2.7 status

gt;> selectively filter stuff in after that in the interest of convergence. >>>> >>>> Thoughts welcome! >>>> >>>> Thanks, >>>> +Vinod >>>> >>>> On Mar 1, 2015, at 11:58 AM, Arun Murthy wrote: >>>&g

Re: 2.7 status

@hadoop.apache.org; Hadoop Common Subject: Re: 2.7 status This is the filter I am using: https://issues.apache.org/jira/issues/?filter=12330598 +Vinod On Mar 25, 2015, at 11:47 AM, Konstantin Shvachko wrote: > Progress is good! > What are the four blockers? > Could you please mark them as such in

Re: 2.7 status

JIRA went down and going back up again, we will need > >> to converge. > >>>>> > >>>>> Unless I see objections, I plan to cut a branch this weekend and > >> selectively filter stuff in after that in the interest of convergence. >

Re: 2.7 status

onverge. >>>>> >>>>> Unless I see objections, I plan to cut a branch this weekend and >> selectively filter stuff in after that in the interest of convergence. >>>>> >>>>> Thoughts welcome! >>>>> >>>>> Thanks, >>>>> +Vinod

Re: 2.7 status

. >> >>> >> >>> Unless I see objections, I plan to cut a branch this weekend and >> selectively filter stuff in after that in the interest of convergence. >> >>> >> >>> Thoughts welcome! >> >>> >> >>> Thank

Re: 2.7 status

to cut a branch this weekend and > selectively filter stuff in after that in the interest of convergence. > >>> > >>> Thoughts welcome! > >>> > >>> Thanks, > >>> +Vinod > >>> > >>> On Mar 1, 2015, at 11:58 AM, Arun

Re: 2.7 status

;> >>> Thoughts welcome! >>> >>> Thanks, >>> +Vinod >>> >>> On Mar 1, 2015, at 11:58 AM, Arun Murthy wrote: >>> >>>> Sounds good, thanks for the help Vinod! >>>> >>>> Arun >>>>

Re: 2.7 status

hts welcome! >> >> Thanks, >> +Vinod >> >> On Mar 1, 2015, at 11:58 AM, Arun Murthy wrote: >> >>> Sounds good, thanks for the help Vinod! >>> >>> Arun >>> >>> ____________ >>> F

Re: 2.7 status

>> Sounds good, thanks for the help Vinod! >> >> Arun >> >> >> From: Vinod Kumar Vavilapalli >> Sent: Sunday, March 01, 2015 11:43 AM >> To: Hadoop Common; Jason Lowe; Arun Murthy >> Subject: R

Re: 2.7 status

wrote: > Sounds good, thanks for the help Vinod! > > Arun > > > From: Vinod Kumar Vavilapalli > Sent: Sunday, March 01, 2015 11:43 AM > To: Hadoop Common; Jason Lowe; Arun Murthy > Subject: Re: 2.7 status > > Agreed. Ho

RE: 2.7 status

Kumar Vavilapalli [mailto:vino...@hortonworks.com] Sent: Tuesday, March 03, 2015 11:31 AM To: Zheng, Kai Cc: mapreduce-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; Hadoop Common; yarn-...@hadoop.apache.org Subject: Re: 2.7 status Kai, please ping the reviewers that were already looking at

Re: 2.7 status

.@cloudera.com] > Sent: Monday, March 02, 2015 4:46 AM > To: hdfs-dev@hadoop.apache.org > Cc: Vinod Kumar Vavilapalli; Hadoop Common; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > Subject: Re: 2.7 status > > Hi, > > Thanks for working on 2.7 release.

Re: 2.7 status

wrote: Sounds good, thanks for the help Vinod! Arun From: Vinod Kumar Vavilapalli Sent: Sunday, March 01, 2015 11:43 AM To: Hadoop Common; Jason Lowe; Arun Murthy Subject: Re: 2.7 status Agreed. How about we roll an RC end of this week? As a Java 7+ relea

Re: 2.7 status

apreduce-...@hadoop.apache.org; > yarn-...@hadoop.apache.org > Subject: Re: 2.7 status > > Hi, > > Thanks for working on 2.7 release. > > Currently the fallback from KerberosAuthenticator to PseudoAuthenticator is > enabled by default in a hardcoded way. HAOOP-10895 changes the de

RE: 2.7 status

Common; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: 2.7 status Hi, Thanks for working on 2.7 release. Currently the fallback from KerberosAuthenticator to PseudoAuthenticator is enabled by default in a hardcoded way. HAOOP-10895 changes the default and requires

Re: 2.7 status

15 at 11:58 AM, Arun Murthy wrote: > Sounds good, thanks for the help Vinod! > > Arun > > > From: Vinod Kumar Vavilapalli > Sent: Sunday, March 01, 2015 11:43 AM > To: Hadoop Common; Jason Lowe; Arun Murthy > Subject: Re: 2.7 statu

Re: 2.7 status

unday, March 01, 2015 11:43 AM > To: Hadoop Common; Jason Lowe; Arun Murthy > Subject: Re: 2.7 status > > Agreed. How about we roll an RC end of this week? As a Java 7+ release with > features, patches that already got in? > > Here's a filter tracking blocker tickets -

Re: 2.7 status

Sounds good, thanks for the help Vinod! Arun From: Vinod Kumar Vavilapalli Sent: Sunday, March 01, 2015 11:43 AM To: Hadoop Common; Jason Lowe; Arun Murthy Subject: Re: 2.7 status Agreed. How about we roll an RC end of this week? As a Java 7+ release

Re: 2.7 status

Allen, can you make that JIRA a blocker with that rationale so that it can be discussed so on the JIRA? Thanks +Vinod On Feb 14, 2015, at 9:30 AM, Allen Wittenauer wrote: > > IMO, HDFS-5796 (in some form or another) is a blocker for 2.7. > > Right now, DFS browsing is pretty much broken on

Re: 2.7 status

Hi Ravi, Only one patch on that umbrella JIRA is PA. And others don't have patches. Are they being actively worked on and can they get in a week or so? Given the delay in 2.7 already, does it make sense to roll this umbrella over to 2.8? Thanks, +Vinod On Feb 14, 2015, at 8:56 AM, Ravi Prakash

Re: 2.7 status

>> thanks, >> Arun >> >> >> From: Jason Lowe >> Sent: Friday, February 13, 2015 8:11 AM >> To: common-...@hadoop.apache.org >> Subject: Re: 2.7 status >> >> I'd like to see a 2.7 release soone

Re: 2.7 status

IMO, HDFS-5796 (in some form or another) is a blocker for 2.7. Right now, DFS browsing is pretty much broken on secure systems when a hadoop-auth-compatible plugin is in use. The "fix" (HDFS-5716) introduced (what appears to be) an incompatible and undocumented method to provide auth versus

Re: 2.7 status

I would like the improvements to the Namenode UI be included in 2.7 too. HDFS-7588. All the code is ready and we can try to get as much of it in as possible piecemeal. On Saturday, February 14, 2015 3:52 AM, Steve Loughran wrote: On 14 February 2015 at 00:37:07, Karthik Kambatl

Re: 2.7 status

On 14 February 2015 at 00:37:07, Karthik Kambatla (ka...@cloudera.com) wrote: 2 weeks from now (end of Feb) sounds reasonable. The one feature I would like for to be included is shared-cache: we are pretty close - two more main items to take care of. In an offline c

Re: 2.7 status

roll fwd a 2.7 ASAP with all the goodies. > > What sort of timing makes sense? 2 week hence? > > thanks, > Arun > > > From: Jason Lowe > Sent: Friday, February 13, 2015 8:11 AM > To: common-...@hadoop.apache.org > Subject

Re: 2.7 status

Subject: Re: 2.7 status I'd like to see a 2.7 release sooner than later. It has been almost 3 months since Hadoop 2.6 was released, and there have already been 634 JIRAs committed to 2.7. That's a lot of changes waiting for an official release. https://issues.apache.org/jira/issues/?j