Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 8 Aug 2016 13:58:20 +0000 (UTC)
From: "Anatoli Shein (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12991875.1469204756000.249154.1470664700735@Atlassian.JIRA>
In-Reply-To: <JIRA.12991875.1469204756000@Atlassian.JIRA>
References: <JIRA.12991875.1469204756000@Atlassian.JIRA> <JIRA.12991875.1469204756629@arcas>
Subject: [jira] [Updated] (HDFS-10679) libhdfs++: Implement parallel find
 with wildcards tool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 08 Aug 2016 13:58:22 -0000


     [ https://issues.apache.org/jira/browse/HDFS-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anatoli Shein updated HDFS-10679:
---------------------------------
    Attachment: HDFS-10679.HDFS-8707.002.patch

Quick fix in async code

> libhdfs++: Implement parallel find with wildcards tool
> ------------------------------------------------------
>
>                 Key: HDFS-10679
>                 URL: https://issues.apache.org/jira/browse/HDFS-10679
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Anatoli Shein
>            Assignee: Anatoli Shein
>         Attachments: HDFS-10679.HDFS-8707.000.patch, HDFS-10679.HDFS-8707.001.patch, HDFS-10679.HDFS-8707.002.patch
>
>
> The find tool will issue the GetListing namenode operation on a given directory, and filter the results using posix globbing library.
> If the recursive option is selected, for each returned entry that is a directory the tool will issue another asynchronous call GetListing and repeat the result processing in a recursive fashion.
> One implementation issue that needs to be addressed is the way how results are returned back to the user: we can either buffer the results and return them to the user in bulk, or we can return results continuously as they arrive. While buffering would be an easier solution, returning results as they arrive would be more beneficial to the user in terms of performance, since the result processing can start as soon as the first results arrive without any delay. In order to do that we need the user to use a loop to process arriving results, and we need to send a special message back to the user when the search is over.


--
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