Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DF07410AFC for ; Mon, 20 Jan 2014 18:46:59 +0000 (UTC) Received: (qmail 38837 invoked by uid 500); 20 Jan 2014 18:46:52 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 38640 invoked by uid 500); 20 Jan 2014 18:46:52 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 38633 invoked by uid 99); 20 Jan 2014 18:46:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jan 2014 18:46:52 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [62.134.46.9] (HELO mx11.unify.com) (62.134.46.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jan 2014 18:46:44 +0000 Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 5EA311EB84E1 for ; Mon, 20 Jan 2014 19:46:23 +0100 (CET) Received: from MCHP04MSX.global-ad.net ([169.254.1.183]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Mon, 20 Jan 2014 19:46:23 +0100 From: "Rananavare, Sunil" To: "user@hadoop.apache.org" Subject: hadoop problem tracking Thread-Topic: hadoop problem tracking Thread-Index: Ac8WD+maiq91cAn+Qwid/VAa/krLGg== Date: Mon, 20 Jan 2014 18:46:23 +0000 Message-ID: <98240E05A256D1499E557B3DC3C51B6517957490@MCHP04MSX.global-ad.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.29.42.225] Content-Type: multipart/alternative; boundary="_000_98240E05A256D1499E557B3DC3C51B6517957490MCHP04MSXglobal_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_98240E05A256D1499E557B3DC3C51B6517957490MCHP04MSXglobal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, we are new to hadoop and trying to use open source apache hadoop (2.2.0= ) with IBM JDK V7.0. We had to compile hadoop components (e.g. pig, hive, e= tc.) with IBM JDK (since original distribution worked with Oracle JRE but f= ailed on IBM JRE) however; we discovered a few compilation errors. Here are= a few examples, a. Requires that jetty_util is added to the pom.xml, see https://issue= s.apache.org/jira/browse/HADOOP-10110 using the patch instructions. b. Requires that serialization package reference in XmlEditsVisitor.ja= va is replaced (com.sun.org.apache.xml.internal.serialize -> org.apache.xml= .serialize) (for instance https://www.ibm.com/developerworks/community/foru= ms/html/topic?id=3D77777777-0000-0000-0000-000014066399#77777777-0000-0000-= 0000-000014066555). c. Requires that Sun security package is replaced with corresponding I= BM package in KeyStoreTestUtil.java (sun.security.x509 -> com.ibm.security.= x509) (for example http://www-01.ibm.com/support/docview.wss?uid=3Dswg1IV20= 285). d. The bug discovered and corrected by HortonWorks in FloatSplitter.ja= va in build 2.2.0.6.0-76 (lowClausePrefix + Double.toString(curUpper), -> l= owClausePrefix + Double.toString(curLower)). After researching a bit it appears that these issues are known and require = some minor code changes (as mentioned above). I am assuming some of these s= uggested code changes are probably being approved or in the processes of be= ing incorporated into the future hadoop releases (0.2.3 or 3.0). I am wonde= ring what the 'official' process is to handle situations like this. Are we = allowed to make such suggested code changes in our local copy of hadoop dis= tributions and maintain these changes in our private repository until the t= ime when the "official" fixes are available in the released hadoop distribu= tions? If so, is this approach Ok from the Apache licensing agreement stand= point? I am sure this problem is not new and some of you might have resolved this.= I would really appreciate your comments/advice. Best regards, Sunil --_000_98240E05A256D1499E557B3DC3C51B6517957490MCHP04MSXglobal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi, we are new to hadoop and trying to use open sour= ce apache hadoop (2.2.0) with IBM JDK V7.0. We had to compile hadoop compon= ents (e.g. pig, hive, etc.) with IBM JDK (since original distribution worke= d with Oracle JRE but failed on IBM JRE) however; we discovered a few compilation errors. Here are a few examp= les,

 

a.&= nbsp;     Requires that = jetty_util is added to the pom.xml, see https://issu= es.apache.org/jira/browse/HADOOP-10110 using the patch instructions.

b.&= nbsp;     Requires that = serialization package reference in XmlEditsVisitor.java is replaced (com.su= n.org.apache.xml.internal.serialize -> org.apache.xml.serialize) (for in= stance https://www.ibm.com/developerworks/community/forums/html/topic?id=3D7777777= 7-0000-0000-0000-000014066399#77777777-0000-0000-0000-000014066555).

c.&= nbsp;     Requires that = Sun security package is replaced with corresponding IBM package in KeyStore= TestUtil.java (sun.security.x509 -> com.ibm.security.x509) (for example htt= p://www-01.ibm.com/support/docview.wss?uid=3Dswg1IV20285).

d.&= nbsp;     The bug discov= ered and corrected by HortonWorks in FloatSplitter.java in build 2.2.0.6.0-= 76 (lowClausePrefix + Double.toString(curUpper), -> lowClausePrefix = + Double.toString(curLower)).

 

After researching a bit it appears that these issues= are known and require some minor code changes (as mentioned above). I am a= ssuming some of these suggested code changes are probably being approved or= in the processes of being incorporated into the future hadoop releases (0.2.3 or 3.0). I am wondering what the &#= 8216;official’ process is to handle situations like this. Are we allo= wed to make such suggested code changes in our local copy of hadoop distrib= utions and maintain these changes in our private repository until the time when the “official” fixes are availa= ble in the released hadoop distributions? If so, is this approach Ok from t= he Apache licensing agreement standpoint?

 

I am sure this problem is not new and some of you mi= ght have resolved this. I would really appreciate your comments/advice.

 

Best regards,

Sunil

--_000_98240E05A256D1499E557B3DC3C51B6517957490MCHP04MSXglobal_--