Distributed Lucene : A distributed free text index for Hadoop


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Distributed Lucene : A distributed free text index for Hadoop
# 1  
Old 06-09-2008
Distributed Lucene : A distributed free text index for Hadoop

HPL-2008-64 Distributed Lucene : A distributed free text index for Hadoop - Butler, Mark H.; Rutherford, James
Keyword(s): distributed, high availability, free text, parallel, search
Abstract: This technical report described a parallel, distributed free text index written at HP Labs called Distributed Lucene. Distributed Lucene is based on two Apache open source projects, Lucene and Hadoop. It was written to gain a better understanding of the Apache Hadoop architecture, which is derived f ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

distributed filesystem over internet/VPN

On this forum was already posted similar question, but it was 4 years ago and didn't give me answers. I have two groups of engineers that works in far locations connected via VPN. Physically, the connection is a DSL. Currently we have a linux server in one location that provide files over... (4 Replies)
Discussion started by: Domino
4 Replies

2. Programming

Distributed Automation kill()

Ok, so Ive been stumped by this problem for the last 3 days, and my exploration is reaching its limitations... The key idea is that at any moment in time, the automation controller could theoretically have any number of threads open to any number of node machines running any number of... (2 Replies)
Discussion started by: jjinno
2 Replies

3. High Performance Computing

Grid vs. Parallel vs. Distributed

Hello all, I was wondering if someone could either explain or maybe point me to another article somewhere that explains the difference between: distributed computing grid computing parallel computing I see these terms thrown around a lot in server and cluster environments, but I'd like a... (2 Replies)
Discussion started by: Heathe_Kyle
2 Replies

4. Programming

Creating a Unique ID on distributed systems

Hi, How do you actually create a unique ID on a distributed system. I looked at gethostid but the man page says that its not guaranteed to be unique. Also using the IP address does not seem to be a feasible solution. Is there a function call or mechanism by which this is possible when even the... (4 Replies)
Discussion started by: pic
4 Replies

5. UNIX for Dummies Questions & Answers

Distributed

I've downloaded distributed latest build for dnetc, and I think i installed it. Not sure where the excicuteable would be. Any help? i realize this is a little ambigious, so I can allways reintstall it if i know how to put it in a specific directory.. does anyone know if VNC works for the Intel... (3 Replies)
Discussion started by: veitcha
3 Replies
Login or Register to Ask a Question
docidx_lang_cmdref(n)						Documentation tools					     docidx_lang_cmdref(n)

__________________________________________________________________________________________________________________________________________________

NAME
docidx_lang_cmdref - docidx language command reference SYNOPSIS
comment plaintext include filename index_begin text title index_end key text lb manpage file text rb url url label vset varname value vset varname _________________________________________________________________ DESCRIPTION
This document specifies both names and syntax of all the commands which together are the docidx markup language, version 1. As this docu- ment is intended to be a reference the commands are listed in alphabetical order, and the descriptions are relatively short. A beginner should read the much more informally written docidx language introduction first. COMMANDS
comment plaintext Index markup. The argument text is marked up as a comment standing outside of the actual text of the document. Main use is in free- form text. include filename Templating. The contents of the named file are interpreted as text written in the docidx markup and processed in the place of the include command. The markup in the file has to be self-contained. It is not possible for a markup command to cross the file bound- aries. index_begin text title Document structure. The command to start an index. The arguments are a label for the whole group of documents the index refers to (text) and the overall title text for the index (title), without markup. The label often is the name of the package (or extension) the documents belong to. index_end Document structure. Command to end an index. Anything in the document coming after this command is in error. key text Index structure. This command adds the keyword text to the index. lb Text. The command is replaced with a left bracket. Use in free-form text. Required to avoid interpretation of a left bracket as the start of a markup command. Its usage is restricted to the arguments of other markup commands. manpage file text Index structure. This command adds an element to the index which refers to a document. The document is specified through the sym- bolic name file. The text argument is used to label the reference. Symbolic names are used to preserve the convertibility of this format to any output format. The actual name of the file will be inserted by the chosen formatting engine when converting the input. This will be based on a mapping from symbolic to actual names given to the engine. rb Text. The command is replaced with a right bracket. Use in free-form text. Required to avoid interpretation of a right bracket as the end of a markup command. Its usage is restricted to the arguments of other commands. url url label Index structure. This is the second command to add an element to the index. To refer to a document it is not using a symbolic name however, but a (possibly format-specific) url describing the exact location of the document indexed here. vset varname value Templating. In this form the command sets the named document variable to the specified value. It does not generate output. I.e. the command is replaced by the empty string. vset varname Templating. In this form the command is replaced by the value of the named document variable BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category doctools of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. SEE ALSO
docidx_intro, docidx_lang_faq, docidx_lang_intro, docidx_lang_syntax KEYWORDS
docidx commands, docidx language, docidx markup, markup, semantic markup COPYRIGHT
Copyright (c) 2007 Andreas Kupries <andreas_kupries@users.sourceforge.net> doctools 1.0 docidx_lang_cmdref(n)