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 4C12C200B72 for ; Thu, 11 Aug 2016 10:47:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4AE15160A94; Thu, 11 Aug 2016 08:47:24 +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 9131D160A85 for ; Thu, 11 Aug 2016 10:47:23 +0200 (CEST) Received: (qmail 43479 invoked by uid 500); 11 Aug 2016 08:47:22 -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 43262 invoked by uid 99); 11 Aug 2016 08:47:22 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2016 08:47:22 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1BFA32C02AE for ; Thu, 11 Aug 2016 08:47:22 +0000 (UTC) Date: Thu, 11 Aug 2016 08:47:22 +0000 (UTC) From: "Surendra Singh Lilhore (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-10608) Include event for AddBlock in Inotify Event Stream MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 11 Aug 2016 08:47:24 -0000 [ https://issues.apache.org/jira/browse/HDFS-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416891#comment-15416891 ] Surendra Singh Lilhore commented on HDFS-10608: ----------------------------------------------- bq. Is that really the case? I haven't seen much change in the Block API in many years. We need to follow the rules :) I feel we can create fields directly in event class only. For example: {code} public static class AddBlockEvent extends Event { private String path; private String blockPoolId; private String newBlockName; private long newBlockGenStamp; private String penultimateBlkName; private long penultimateBlkGenStamp; private long numBytesInPenultimateBlk; . . } {code} > Include event for AddBlock in Inotify Event Stream > -------------------------------------------------- > > Key: HDFS-10608 > URL: https://issues.apache.org/jira/browse/HDFS-10608 > Project: Hadoop HDFS > Issue Type: Task > Reporter: churro morales > Priority: Minor > Attachments: HDFS-10608.patch, HDFS-10608.v1.patch > > > It would be nice to have an AddBlockEvent in the INotify pipeline. Based on discussions from mailing list: > http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201607.mbox/%3C1467743792.4040080.657624289.7BE240AD%40webmail.messagingengine.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org