[
https://issues.apache.org/jira/browse/SOLR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537924
]
Grant Ingersoll commented on SOLR-342:
--------------------------------------
{quote}
+1
ramBufferSizeMB is now the default in Lucene AFAIK.
I think perhaps 32MB might be a good default.
{quote}
The other thing is, Lucene actually supports setting both, and flushes based on
whichever one is hit first. Is this worth supporting?
{quote}
For Solr, you never would want to use it. trying to catch a glimpse of new
segments as they are flushed leads to an inconsistent view of the index since
docs haven't been deleted yet.
{quote}
Should we even expose this, then? It seems like we should just make it false.
I will write up more in the changes.
> 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: 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.
