Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1156137668.1236183478814.JavaMail.jira@brutus>
Date: Wed, 4 Mar 2009 08:17:58 -0800 (PST)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1045) Build Solr index using Hadoop
 MapReduce
In-Reply-To: <491269315.1236035336168.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678770#action_12678770 ] 

Yonik Seeley commented on SOLR-1045:
------------------------------------

The "solr index" is normally just a Lucene index which has been indexed according to the particular schema.
There are exceptions, as you have noted:
 - the spell check index
 - ExternalFileField

It's worth keeping these in mind, and perhaps could be useful to be able to handle at some point, but it certainly doesn't seem critical.

> Build Solr index using Hadoop MapReduce
> ---------------------------------------
>
>                 Key: SOLR-1045
>                 URL: https://issues.apache.org/jira/browse/SOLR-1045
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ning Li
>         Attachments: SOLR-1045.0.patch
>
>
> The goal is a contrib module that builds Solr index using Hadoop MapReduce.
> It is different from the Solr support in Nutch. The Solr support in Nutch sends a document to a Solr server in a reduce task. Here, the goal is to build/update Solr index within map/reduce tasks. Also, it achieves better parallelism when the number of map tasks is greater than the number of reduce tasks, which is usually the case.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.