Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99EBB11A46 for ; Tue, 5 Aug 2014 16:06:12 +0000 (UTC) Received: (qmail 85148 invoked by uid 500); 5 Aug 2014 16:06:02 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 85085 invoked by uid 500); 5 Aug 2014 16:06:02 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 85069 invoked by uid 99); 5 Aug 2014 16:06:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 16:06:02 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Aug 2014 16:05:57 +0000 Received: by mail-ig0-f182.google.com with SMTP id c1so1402390igq.15 for ; Tue, 05 Aug 2014 09:05:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=IkWdGMME6qevv2AJkXweeYlyrlHNrRZKEN/b9Jr+nvY=; b=Lae7Aeofq0tSKJ+w/Msn/Tgx2+Mw2uxN+3HCAg8Fh+rslV+vMFVqxyHZTcWo2bKnFv 7QCFrla+LHbXwZ+34hQvn/LklYXlOlWMnccIiAWhmp+Jb1kC/BNyXrrchp2CLq/v+l2f UFO8n4UZ2VcrICEgcMslrjDpV9mGZPUp/QaiyXTPt328pr+ODUI14ua0F0QDybYqPg/U OG2bMyZcYg4ZtlEOfQzfpFQzuoDNoOjSw0IenIszaNdDUQvL5nFuznNswxYJpteWz8BN 8RbIPcVFzYl+okxr6F42UlrLkUfPCEMUJifKSVk2mUQ79DCNMoXPuIIlWN/Rt40Zdv1T VIqw== X-Gm-Message-State: ALoCoQlDq2GcBFUTK/AyfTVvQawl1lgKJ+0joAgv3fYE0jJyCW95jq+MO5QypJVZTLZchFFfq2de X-Received: by 10.42.106.145 with SMTP id z17mr6755030ico.82.1407254736456; Tue, 05 Aug 2014 09:05:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.137.42 with HTTP; Tue, 5 Aug 2014 09:05:16 -0700 (PDT) In-Reply-To: References: From: Michael Della Bitta Date: Tue, 5 Aug 2014 12:05:16 -0400 Message-ID: Subject: Re: solr over hdfs for accessing/ changing indexes outside solr To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=20cf30363b4bacdf6204ffe406c2 X-Virus-Checked: Checked by ClamAV on apache.org --20cf30363b4bacdf6204ffe406c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Probably the "most correct" way to modify the index would be to use the Solr REST API to push your changes out. Another thing you might want to look at is Lilly. Basically it's a way to set up a Solr collection as an HBase replication target, so changes to your HBase table would automatically propagate over to Solr. http://www.ngdata.com/on-lily-hbase-hadoop-and-solr/ Michael Della Bitta Applications Developer o: +1 646 532 3062 appinions inc. =E2=80=9CThe Science of Influence Marketing=E2=80=9D 18 East 41st Street New York, NY 10017 t: @appinions | g+: plus.google.com/appinions w: appinions.com On Tue, Aug 5, 2014 at 9:04 AM, Ali Nazemian wrote: > Dear all, > Hi, > I changed solr 4.9 to write index and data on hdfs. Now I am going to > connect to those data from the outside of solr for changing some of the > values. Could somebody please tell me how that is possible? Suppose I am > using Hbase over hdfs for do these changes. > Best regards. > > -- > A.Nazemian > --20cf30363b4bacdf6204ffe406c2--