Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Hadoop in Fedora updated to 2.2.0


Copy link to this message
-
Re: Hadoop in Fedora updated to 2.2.0
I've just been through some of these as part of my background project, "fix
up the POMs" https://issues.apache.org/jira/browse/HADOOP-9991.
   1. I've applied the simple low/risk ones.
   2. I've not done the bookkeeper one, as people working with that code
   need to play with it first.
   3. I've not touched anything related to {jersey, tomcat, jetty}

This is more than just a java6/7 issue, is is that Jetty has been very
brittle in the past, and there's code in hadoop to detect when it's not
actually servicing requests properly. Moving up Jetty/web server versions
is something that needs to be done carefull and with consensus -and once
you leave Jetty alone, I don't know where the jersey and tomcat changes go.

There is always the option of s/jetty/r/grizzly/

-steve
On 1 November 2013 14:57, Robert Rati <[EMAIL PROTECTED]> wrote:

> Putting the java 6 vs java 7 issue aside, what about the other patches to
> update dependencies?  Can those be looked at an planned for inclusion into
> a releation?
>
> Rob
>
>
> On 10/31/2013 05:51 PM, Andrew Wang wrote:
>
>> I'm in agreement with Steve on this one. We're aware that Java 6 is EOL,
>> but we can't drop support for the lifetime of the 2.x line since it's a
>> (very) incompatible change. AFAIK a 3.x release fixing this isn't on any
>> of
>> our horizons yet.
>>
>> Best,
>> Andrew
>>
>>
>> On Thu, Oct 31, 2013 at 6:15 AM, Robert Rati <[EMAIL PROTECTED]> wrote:
>>
>>  https://issues.apache.org/****jira/browse/HADOOP-9594<https:
>>> //issues.apache.org/**jira/browse/HADOOP-9594>
>>>
>>>> <https:**//issues.apache.org/jira/**browse/HADOOP-9594<http
>>>>> s://issues.apache.org/jira/browse/HADOOP-9594>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/MAPREDUCE-5431<htt
>>>>> ps://issues.apache.org/**jira/browse/MAPREDUCE-5431>
>>>>> <htt**ps://issues.apache.org/jira/**browse/MAPREDUCE-5431<h
>>>>> ttps://issues.apache.org/jira/browse/MAPREDUCE-5431>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-9611<https:
>>>>> //issues.apache.org/**jira/browse/HADOOP-9611>
>>>>> <https:**//issues.apache.org/jira/**browse/HADOOP-9611<http
>>>>> s://issues.apache.org/jira/browse/HADOOP-9611>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-9613<https:
>>>>> //issues.apache.org/**jira/browse/HADOOP-9613>
>>>>> <https:**//issues.apache.org/jira/**browse/HADOOP-9613<http
>>>>> s://issues.apache.org/jira/browse/HADOOP-9613>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-9623<https:
>>>>> //issues.apache.org/**jira/browse/HADOOP-9623>
>>>>> <https:**//issues.apache.org/jira/**browse/HADOOP-9623<http
>>>>> s://issues.apache.org/jira/browse/HADOOP-9623>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HDFS-5411<https://
>>>>> issues.apache.org/**jira/browse/HDFS-5411>
>>>>> <https://**issues.apache.org/jira/browse/**HDFS-5411<https:
>>>>> //issues.apache.org/jira/browse/HDFS-5411>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-10067<https
>>>>> ://issues.apache.org/**jira/browse/HADOOP-10067>
>>>>> <https**://issues.apache.org/jira/**browse/HADOOP-10067<htt
>>>>> ps://issues.apache.org/jira/browse/HADOOP-10067>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HDFS-5075<https://
>>>>> issues.apache.org/**jira/browse/HDFS-5075>
>>>>> <https://**issues.apache.org/jira/browse/**HDFS-5075<https:
>>>>> //issues.apache.org/jira/browse/HDFS-5075>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-10068<https
>>>>> ://issues.apache.org/**jira/browse/HADOOP-10068>
>>>>> <https**://issues.apache.org/jira/**browse/HADOOP-10068<htt
>>>>> ps://issues.apache.org/jira/browse/HADOOP-10068>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-10075<https
>>>>> ://issues.apache.org/**jira/browse/HADOOP-10075>
>>>>> <https**://issues.apache.org/jira/**browse/HADOOP-10075<htt
>>>>> ps://issues.apache.org/jira/browse/HADOOP-10075>
>>>>>
>>>>>>
>>>>>>  https://issues.apache.org/****jira/browse/HADOOP-10076<https

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.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB