I think Lily implements search using Solr distributed search (eg, external to HBase), so it's possible for a server to fail and then all queries will fail? Also then there's overhead from reading the WAL from an external process?
2011/5/13 Frédéric Fondement <[email protected]>: > Hello, > > I think that it's the purpose of lily (http://www.lilyproject.org/), though > you have to use lily's API instead of HBase client API. I mean it's not > intended to be plugged to existing HBase data. Am I wrong ? > > Le 13/05/11 18:35, highpointe a écrit : >> >> Jason, >> >> Where could one find that patch. Also your implementation of Solr to Hbase >> is definitely something I'd love to hear about. >> >> HP >> Sent from my iPhone >> >> On May 13, 2011, at 10:00 AM, Jason Rutherglen<[email protected]> >> wrote: >> >>> Paul, >>> >>> I have a patch to implement Lucene in HBase - HBASE-3529. It's a work >>> in progress limited primarily by time. >>> >>> For a web UI I'll probably eventually integrate Solr at some point, >>> which would provide a basic UI, though it'd need to be modified to >>> account for column families. Is this what you're looking for? >>> >>> Jason >>> >>> On Fri, May 13, 2011 at 8:52 AM, Sterk, Paul (Contractor) >>> <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> >>>> >>>> I am looking for a web based query tool that is able to query Hbase >>>> tables and columns. Can someone point me to any? I want to be able to >>>> create secondary indexes on Hbase tables then issue queries against >>>> similar to Solr/Lucene. For example: 'find all transactions with >>>> transaction number 9040' with a query such as >>>> 'TransactionMaster.transaction_nbr:9040'. >>>> >>>> >>>> >>>> I have found this tool so far: >>>> http://sourceforge.net/projects/hbaseexplorer/ >>>> >>>> >>>> >>>> Please let me know if there are any others. >>>> >>>> >>>> >>>> Thanks in advance, >>>> >>>> Paul >>>> >>>> This message, including any attachments, is the property of Sears >>>> Holdings Corporation and/or one of its subsidiaries. It is confidential and >>>> may contain proprietary or legally privileged information. If you are not >>>> the intended recipient, please delete it without reading the contents. >>>> Thank >>>> you. >>>> > >
