Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-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 424B11140F for ; Thu, 24 Jul 2014 14:27:40 +0000 (UTC) Received: (qmail 32226 invoked by uid 500); 24 Jul 2014 14:27:40 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 32199 invoked by uid 500); 24 Jul 2014 14:27:40 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 32180 invoked by uid 99); 24 Jul 2014 14:27:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 14:27:39 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.65.160.92] (HELO nbfkord-smmo05.seg.att.com) (209.65.160.92) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 14:27:32 +0000 Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.2-0) over TLS secured channel with ESMTP id fb711d35.0.5558090.00-2250.15518195.nbfkord-smmo05.seg.att.com (envelope-from ); Thu, 24 Jul 2014 14:27:11 +0000 (UTC) X-MXL-Hash: 53d117bf79cd94e8-b726139f2c7a5f8058818da7af89479d3905b3bc Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s6OERApl017318 for ; Thu, 24 Jul 2014 10:27:11 -0400 Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s6OER5cP017232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 24 Jul 2014 10:27:06 -0400 Received: from MOKSCY3MSGHUBAH.ITServices.sbc.com (MOKSCY3MSGHUBAH.itservices.sbc.com [135.188.226.32]) by mlpi407.sfdc.sbc.com (RSA Interceptor) for ; Thu, 24 Jul 2014 14:26:48 GMT Received: from MOKSCY3MSGUSRHH.ITServices.sbc.com ([169.254.8.38]) by MOKSCY3MSGHUBAH.ITServices.sbc.com ([135.188.226.32]) with mapi id 14.03.0174.001; Thu, 24 Jul 2014 09:26:47 -0500 From: "THORMAN, ROBERT D" To: "dev@accumulo.apache.org" Subject: Re: Search Thread-Topic: Search Thread-Index: AQHPofBsjW+c1Zoy9EKo/+2sN9XY6puk9EuAgAABCgCAAc7bAIAHuC8AgAAZAICAAL1zgA== Date: Thu, 24 Jul 2014 14:26:47 +0000 Message-ID: References: <53C81EA5.7010302@gmail.com> <211D3DDA-7209-48DD-BC6B-55F6A7D4158A@clearedgeit.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.210.225.45] Content-Type: text/plain; charset="us-ascii" Content-ID: <26F263BEDE26B34DA0B2A524DE3FA966@LOCAL> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=YYkKEXtf c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a] X-AnalysisOut: [=ofMgfj31e3cA:10 a=4plWEjchykMA:10 a=BLceEmwcHowA:10 a=kj9] X-AnalysisOut: [zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=pGLkceISAAAA:8 a=5L1ViR4ZA] X-AnalysisOut: [AAA:8 a=GQkYeZhHV2qnAzm0mc0A:9 a=CjuIK1q_8ugA:10 a=d3wjIzz] X-AnalysisOut: [8-mQA:10 a=MSl-tDqOz04A:10 a=7f50zUBqVtAA:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)] X-MAIL-FROM: X-SOURCE-IP: [144.160.229.24] X-Virus-Checked: Checked by ClamAV on apache.org David, How would you tie the two streams back together so that data is not duplicated but referenced by SolrCloud into Accumulo? v/r Bob Thorman Principal Big Data Engineer AT&T Big Data CoE 2900 W. Plano Parkway Plano, TX 75075 972-658-1714 On 7/23/14, 5:09 PM, "David Medinets" wrote: >Ingest to a queue. Have two processes subscribe to the queue. One >pushing into Accumulo and the other pushing into SolrCloud. Why >tightly couple the capabilities? > >On Wed, Jul 23, 2014 at 4:39 PM, Roshan Punnoose >wrote: >> Is there a way to tie into the write process in Accumulo? Maybe just >>use an >> Iterator that worked on compaction to send data to blur/solr? I have >>seen >> something similar in Cassandra, a data hook to save data in Solr. >> >> >> On Fri, Jul 18, 2014 at 6:46 PM, Nehal Mehta wrote: >> >>> We were trying to do so, but adding visibility while adding/searching >>> documents needs lot more thinking. Adding visibility to core search >>>engine >>> needs changes to algorithm and that does not make it very scalable. >>> Integration besides granular visibility is very doable. and we had >>>taken >>> inspiration from Solandra. >>> >>> Obviously if we can get it done it adds lot of value. I believe Sqrrl >>> people have already done it, are they thinking to open source it >>>anytime in >>> future? >>> >>> >>> On Thu, Jul 17, 2014 at 3:09 PM, Donald Miner >>> wrote: >>> >>> > We briefly toyed with blur on accumulo but didnt get too far just >>>because >>> > it was obe. I think that would be cool. >>> > >>> > > On Jul 17, 2014, at 3:06 PM, Josh Elser >>>wrote: >>> > > >>> > > It's definitely possible. I remember hearing about someone doing >>>lucene >>> > on top of Accumulo once, but I don't recall seeing a nice package >>>with a >>> > bow on top. >>> > > >>> > >> On 7/17/14, 2:53 PM, THORMAN, ROBERT D wrote: >>> > >> What lexical search package (like lucene/solr) has anyone put on >>>top >>> of >>> > accumulo? Is this possible or does everyone just index log files and >>> > documents? >>> > >> >>> > >> v/r >>> > >> Bob Thorman >>> > >> Principal Big Data Engineer >>> > >> AT&T Big Data CoE >>> > >> 2900 W. Plano Parkway >>> > >> Plano, TX 75075 >>> > >> 972-658-1714 >>> > >> >>> > >> >>> > >> >>> > >>>