lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-342) Add support for Lucene's new Indexing and merge features (excluding Document/Field/Token reuse)
Date Thu, 25 Oct 2007 21:30:50 GMT

    [ https://issues.apache.org/jira/browse/SOLR-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537738
] 

Yonik Seeley commented on SOLR-342:
-----------------------------------

> Default is the maxBufferedDocs way, but this could be changed to be the other way around
(and probably should be)

+1
ramBufferSizeMB is now the default in Lucene AFAIK.
I think perhaps 32MB might be a good default.

{quote}luceneAutoCommit [...] Still need to develop recommendations for when to change this.{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.

We do need to document recommended solrconfig.xml changes in CHANGES.txt (at the top in the
migration section we normally have) for people to get these performance gains with existing
configs.

> 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.


Mime
View raw message