From dev-return-32063-apmail-nutch-dev-archive=nutch.apache.org@nutch.apache.org Wed Oct 28 17:29:45 2015 Return-Path: X-Original-To: apmail-nutch-dev-archive@www.apache.org Delivered-To: apmail-nutch-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1AF2F18EE6 for ; Wed, 28 Oct 2015 17:29:45 +0000 (UTC) Received: (qmail 48406 invoked by uid 500); 28 Oct 2015 17:29:28 -0000 Delivered-To: apmail-nutch-dev-archive@nutch.apache.org Received: (qmail 48252 invoked by uid 500); 28 Oct 2015 17:29:28 -0000 Mailing-List: contact dev-help@nutch.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nutch.apache.org Delivered-To: mailing list dev@nutch.apache.org Received: (qmail 47918 invoked by uid 99); 28 Oct 2015 17:29:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2015 17:29:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 159B12C1F61 for ; Wed, 28 Oct 2015 17:29:28 +0000 (UTC) Date: Wed, 28 Oct 2015 17:29:28 +0000 (UTC) From: "Sujen Shah (JIRA)" To: dev@nutch.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NUTCH-2153) Nutch REST API (DB) uses POST instead of GET to request MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NUTCH-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978826#comment-14978826 ] Sujen Shah commented on NUTCH-2153: ----------------------------------- Hi [~ahmadia] and [~chrismattmann], Currently, while using Nutch REST services in local mode, the crawldb job gets executed pretty fast. But if the same is used in a distributed mode, the crawldb job can take up a fair amount of time. So issuing a GET request would make the client wait for a long time for the response. A POST request was used since the crawldb resource is created once a user issues a request and not precomputed (which is usually the case when a GET is used). The /db endpoint still requires development in the part where it can spin up threads for computation like the /job endpoint, and then provide a GET interface to query results. I have tried to use the same concept in the commoncrawldump service as that might also take up time as the amount of data crawled increases. I would like to know what are your thoughts to handle such cases, where issuing a GET requires computation of the resource. Thanks! > Nutch REST API (DB) uses POST instead of GET to request > ------------------------------------------------------- > > Key: NUTCH-2153 > URL: https://issues.apache.org/jira/browse/NUTCH-2153 > Project: Nutch > Issue Type: Bug > Components: REST_api > Affects Versions: 1.11 > Reporter: Aron Ahmadia > Priority: Trivial > Labels: memex > -- This message was sent by Atlassian JIRA (v6.3.4#6332)