[
https://issues.apache.org/jira/browse/SOLR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567221#action_12567221
]
Grant Ingersoll commented on SOLR-342:
--------------------------------------
Direct core meaning embedded, right? It's interesting, b/c I have done a fair
amount of Lucene 2.3 testing w/ Wikipedia (nothing like a free, fairly large
dataset)
Can you reproduce the problem using Lucene directly? (have a look at
contrib/benchmark for a way to get Lucene/Wikipedia up and running quickly)
Also, are there any associated exceptions anywhere in the chain? Or is it just
that your index is bad? Are you starting from a clean index or updating an
existing one?
> Add support for Lucene's new Indexing and merge features (excluding
> Document/Field/Token reuse)
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-342
> URL: https://issues.apache.org/jira/browse/SOLR-342
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Attachments: copyLucene.sh, SOLR-342.patch, SOLR-342.patch,
> SOLR-342.patch, SOLR-342.tar.gz
>
>
> LUCENE-843 adds support for new indexing capabilities using the
> setRAMBufferSizeMB() method that should significantly speed up indexing for
> many applications. To fix this, we will need trunk version of Lucene (or
> wait for the next official release of Lucene)
> Side effect of this is that Lucene's new, faster StandardTokenizer will also
> be incorporated.
> Also need to think about how we want to incorporate the new merge scheduling
> functionality (new default in Lucene is to do merges in a background thread)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
