Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 52961 invoked from network); 5 Oct 2009 03:48:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Oct 2009 03:48:54 -0000 Received: (qmail 67049 invoked by uid 500); 5 Oct 2009 03:48:54 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 66924 invoked by uid 500); 5 Oct 2009 03:48:53 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 66914 invoked by uid 99); 5 Oct 2009 03:48:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 03:48:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jason.hadoop@gmail.com designates 209.85.212.198 as permitted sender) Received: from [209.85.212.198] (HELO mail-vw0-f198.google.com) (209.85.212.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 03:48:42 +0000 Received: by vws36 with SMTP id 36so1567126vws.29 for ; Sun, 04 Oct 2009 20:47:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=lUU6qXjxvs+3p6p+PL9Xz/NtvPsNKXueTBwOcvWZwJs=; b=QorQh0hw3Id1uf0b4ent35FfKbBh+5W8DNuFD43h1PA99FEM6R2y5q9LFSh4181QAc oK2rdZ7qZEzVQToVRKSgoOYCono8hifHg2GVYNuEju2p0/3ojAU7kPyDIwZPusafs/PR XqcpqFW5koNos7JPGVtka+0B+bZ6HyKIH3Qgg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Npl48W7CT3lveSGvxLQLPHUr8aRuJZ1sEHBaOjIOrhcW9YePhFt6jz9nRe0c2LeBb9 k7zyt2JmpD5BCw3EzlMDfnAw8o2HU3IfLpSCFPaPVtXGlCNE7I+lRiZcznR8biO/xm6K /WmroJ8Co4EM3CPtPGFlU0umPhZ0pa9NzCuos= MIME-Version: 1.0 Received: by 10.220.69.169 with SMTP id z41mr8994574vci.31.1254714441368; Sun, 04 Oct 2009 20:47:21 -0700 (PDT) In-Reply-To: <4ac884cb.9713f30a.3f10.ffff9c65@mx.google.com> References: <4ac884cb.9713f30a.3f10.ffff9c65@mx.google.com> Date: Sun, 4 Oct 2009 20:47:21 -0700 Message-ID: <314098690910042047r79355f3ewc0b140a8b524ee64@mail.gmail.com> Subject: Re: katta and hadoop index contrib From: Jason Venner To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e64756269285ea047527f857 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64756269285ea047527f857 Content-Type: text/plain; charset=ISO-8859-1 Currently Katta, will pull the index out of HDFS and deploy it on local disk. HDFS is not known for low latency random access, and index lookups generally require low latency random access. I seem to remember that someone had a patch that allowed lucene to directly access files in hdfs for the index, for readon ly access, but I do not remember the reference. On Sun, Oct 4, 2009 at 4:19 AM, Chandan Tamrakar < chandan.tamrakar@nepasoft.com> wrote: > I was using the hadoop.contrib.index code and was able to make a > distributed Lucene index > > Could then search over that index while it is still in hdfs > > > > Does the Katta project uses same hadoop index-contrib to index the > documents ? > > > > I found that there are also contributions solr-1395 and solr-1301 ( solr > -hadoop ) what would be the best approach to begin with > > > > > > > > Thanks > > > > > > -- Pro Hadoop, a book to guide you from beginner to hadoop mastery, http://www.amazon.com/dp/1430219424?tag=jewlerymall www.prohadoopbook.com a community for Hadoop Professionals --0016e64756269285ea047527f857--