Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E13FA200D33 for ; Wed, 8 Nov 2017 19:58:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DFDA2160C01; Wed, 8 Nov 2017 18:58:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3993D1609E0 for ; Wed, 8 Nov 2017 19:58:09 +0100 (CET) Received: (qmail 84592 invoked by uid 500); 8 Nov 2017 18:58:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 84571 invoked by uid 99); 8 Nov 2017 18:58:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2017 18:58:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7E15EEDEC7 for ; Wed, 8 Nov 2017 18:58:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id hN1gmdLIj1nF for ; Wed, 8 Nov 2017 18:58:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B016561435 for ; Wed, 8 Nov 2017 18:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 37FC0E0E7A for ; Wed, 8 Nov 2017 18:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9C89A240E6 for ; Wed, 8 Nov 2017 18:58:00 +0000 (UTC) Date: Wed, 8 Nov 2017 18:58:00 +0000 (UTC) From: "Nanda kumar (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12549) Ozone: OzoneClient: Support for REST protocol MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Nov 2017 18:58:10 -0000 [ https://issues.apache.org/jira/browse/HDFS-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244543#comment-16244543 ] Nanda kumar commented on HDFS-12549: ------------------------------------ [~xyao], review comments are addressed in patch v004. bq. have you consider using the new JDK8 DateTimeFormatter/ZonedDateTime for the handling of ozone creation/modification timestamp? Thanks for the suggestion, I have modified it accordingly. bq. Please add some comments to it and the default values for OZONE_REST_CLIENT_HTTP_CONNECTION_MAX and maybe some document also in ozone-default.xml Done bq. there are other configurations of PoolingHttpClientConnectionManager that we might want to expose via OzoneConfigKeys in addition to the MaxTotal, e.g., max per route Apart from MaxTotal also added DefaultMaxPerRoute, please let me know if anything else needs to be added. bq. we don't need to instantiate a new data formatter here. The hard coded format string can be replaced by OzoneConsts.OZONE_DATE_FORMAT. Fixed bq. should use the getShortUserName() Fixed bq. executeHttpRequest does not close the response, which causes leaking of the response stream. Since in {{createKey}} and {{getKey}} the {{HttpEntity}} has to be close only when we close the stream, the responsibility of consuming response HttpEntity is given to the caller. I have updated the javadoc to make it explicit to the caller of {{executeHttpRequest}} > Ozone: OzoneClient: Support for REST protocol > --------------------------------------------- > > Key: HDFS-12549 > URL: https://issues.apache.org/jira/browse/HDFS-12549 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Reporter: Nanda kumar > Assignee: Nanda kumar > Attachments: HDFS-12549-HDFS-7240.000.patch, HDFS-12549-HDFS-7240.001.patch, HDFS-12549-HDFS-7240.002.patch, HDFS-12549-HDFS-7240.003.patch, HDFS-12549-HDFS-7240.004.patch > > > Support for REST protocol in OzoneClient. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org