hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Question on hadoop dependencies.
Date Wed, 13 Nov 2013 20:51:12 GMT
Petar,

We've just been through some of 2.3, on the branch
https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2

Most of that was update, apart from moving grizzly and junit to test scope,
we've  not done much.

why do you have a look and help clean things out. I'd particularly like to
see "lean" clients for HDFS, YARN and mapreduce


On 30 October 2013 22:25, Petar Tahchiev <paranoiabla@gmail.com> wrote:

> Hi Roman,
>
> looks like they have already upgraded to 2.2
>
> https://issues.apache.org/jira/browse/SOLR-5382
>
> and will be shipping it SOLR 4.6. I just hope you guys release cleaned 2.3
> first :)
>
>
> 2013/10/30 Roman Shaposhnik <rvs@apache.org>
>
> > On Wed, Oct 30, 2013 at 1:07 PM, Steve Loughran <stevel@hortonworks.com>
> > wrote:
> > > On 30 October 2013 13:07, Petar Tahchiev <paranoiabla@gmail.com>
> wrote:
> > >> So spring-data-solr (1.1.SNAPSHOT) uses solr 4.5.1 (just came out a
> few
> > >> days ago), which uses Hadoop 2.0.5-alpha.
> > >> I would be glad if we can clean up the poms a bit and leave only the
> > >> dependencies
> > >> that hadoop really depend on.
> >
> > To pile on top of what Steve has said -- do you happen to know if there's
> >  a JIRA to re target Solr to depend on Hadoop 2.2.0?
> >
> > Thanks,
> > Roman.
> >
>
>
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611
>

-- 
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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message