Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 3A1D811BD9 for ; Thu, 1 May 2014 13:13:54 +0000 (UTC) Received: (qmail 54447 invoked by uid 500); 1 May 2014 13:13:45 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 54166 invoked by uid 500); 1 May 2014 13:13:45 -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 54159 invoked by uid 99); 1 May 2014 13:13:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 13:13:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smarty.juice@gmail.com designates 209.85.219.49 as permitted sender) Received: from [209.85.219.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 13:13:40 +0000 Received: by mail-oa0-f49.google.com with SMTP id o6so3522870oag.22 for ; Thu, 01 May 2014 06:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=hCC3FfV1uFL86dFAwx4S89pbs5Nn0I52EbSmDMylrYg=; b=0tHKFt1cHkhdwR/PYEF63M9e0LAJOFQnfHCeUVKBKz0F6Y5nq0w2SnZzq6HBEkwjnK gsBpEb5tTr+HetgWaTXcEM3HETaxmIDwMbu4cuWFCsECxLs+y/Nw6DZcnjTw6GcKG6lp AH0yEzsUrLTZBVgcJEv7JhquvIktP2NIwCgtNFZQqgVToxwUy+UuHz9h9gwn0WJcdX71 VOsiL/gUhwE2r5CVRLVoTMcEwuleBU580fjht4/L5gscg0lmvP9UM8PH7fgcMon2bG5V iEYZj6ZuKNoagO18y/XlIpBj39fccCNdCjlkZ5ml1Ht4ERUz4K7qH2WCqFxAsAs1Wkr0 YpNQ== MIME-Version: 1.0 X-Received: by 10.60.40.198 with SMTP id z6mr17047oek.85.1398949997631; Thu, 01 May 2014 06:13:17 -0700 (PDT) Received: by 10.182.74.10 with HTTP; Thu, 1 May 2014 06:13:17 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 May 2014 09:13:17 -0400 Message-ID: Subject: Re: HttpConfig API changes in hadoop 2.4.0 From: Hardik Pandya To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e013cc1f2aadea404f8566d09 X-Virus-Checked: Checked by ClamAV on apache.org --089e013cc1f2aadea404f8566d09 Content-Type: text/plain; charset=UTF-8 https://issues.apache.org/jira/browse/HDFS-5308 On Thu, May 1, 2014 at 8:58 AM, Hardik Pandya wrote: > You are hitting this HDFS-5308. Replace HttpConfig#getSchemePrefix with implicit schemes in HDFS JSP. (Haohui Mai via jing9) > > > > On Wed, Apr 30, 2014 at 6:08 PM, Gaurav Gupta wrote: > >> I am trying to get the container logs url and here is the code snippet >> >> containerLogsUrl = HttpConfig.getSchemePrefix() + this.container.nodeHttpAddress + "/node/containerlogs/" + id + "/" + System.getenv(ApplicationConstants.Environment.USER.toString()); >> >> >> Thanks >> >> Gaurav >> >> >> >> On Wed, Apr 30, 2014 at 3:02 PM, Haohui Mai wrote: >> >>> Hi, >>> >>> Can you describe your use cases, that is, how the prefix is used? >>> Usually you can get around with it by generating relative URLs, which >>> starts at "//". >>> >>> ~Haohui >>> >>> >>> On Wed, Apr 30, 2014 at 2:31 PM, Gaurav Gupta wrote: >>> >>>> Hi, >>>> >>>> I was using hadoop 2.2.0 to build my application. I was using >>>> HttpConfig.getSchemaPrefix() api call. When I updated hadoop to 2.4.0, the >>>> compilation fails for my application and I see that HttpConfig >>>> (org.apache.hadoop.http.HttpConfig) APIs have changed. >>>> >>>> How do I get the schrema Prefix in 2.4? >>>> >>>> Thanks >>>> Gaurav >>>> >>> >>> >>> 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. >> >> >> > --089e013cc1f2aadea404f8566d09 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, May 1, 2014 at = 8:58 AM, Hardik Pandya <smarty.juice@gmail.com> wrote:<= br> 
You are hitting this HDFS-5308. Replace HttpConfig#getSch=
emePrefix with implicit schemes in HDFS JSP. (Haohui Mai via jing9)

On Wed, Apr 30, 2014 at 6:08 PM, Gaurav Gu= pta <gaurav.gopi123@gmail.com> wrote:
I am trying to get the cont= ainer logs url and here is the code snippet
containerLogsUrl=
 =3D HttpConfig.getSche=
mePrefix() + this.container.nodeHttpAddress +<=
/span> "/node/containerlogs/" + i=
d + "/" + Sys=
tem.getenv(ApplicationC=
onstants.Environment.US=
ER.toString());

Thanks
Gaurav
<= div>


On Wed, Apr 30, 2014 at 3:02 PM, Haohui Mai = <hmai@hortonworks.com> wrote:
Hi,

Can = you describe your use cases, that is, how the prefix is used? Usually you c= an get around with it by generating relative URLs, which starts at "//= ".

~Haohui


On Wed, Apr 30, 2014 at 2:31 PM, Gaurav Gupta <gau= rav.gopi123@gmail.com> wrote:
Hi,

I wa= s using hadoop 2.2.0 to build my application. I was using HttpConfig.getSch= emaPrefix() api call. When I updated hadoop to 2.4.0, the compilation fails= for my application and I see that HttpConfig (org.apache.hadoop.http.HttpC= onfig) APIs have changed.=C2=A0

How do I get the schrema Prefix in 2.4?

<= /div>
Thanks
Gaurav


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 comm= unication is strictly prohibited. If you have received this communication i= n error, please contact the sender immediately and delete it from your syst= em. Thank You.



--089e013cc1f2aadea404f8566d09--