Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 371ECD446 for ; Wed, 10 Oct 2012 14:27:04 +0000 (UTC) Received: (qmail 49862 invoked by uid 500); 10 Oct 2012 14:27:03 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 49818 invoked by uid 500); 10 Oct 2012 14:27:03 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 49810 invoked by uid 99); 10 Oct 2012 14:27:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 14:27:03 +0000 Date: Wed, 10 Oct 2012 14:27:03 +0000 (UTC) From: "Michael McCandless (JIRA)" To: dev@lucene.apache.org Message-ID: <1849349921.19959.1349879223057.JavaMail.jiratomcat@arcas> In-Reply-To: <967504482.19864.1349878022933.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (LUCENE-4472) Add setting that prevents merging on updateDocument MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473255#comment-13473255 ] Michael McCandless commented on LUCENE-4472: -------------------------------------------- Neat :) How does ES customize / throttle its merging? Maybe the setting should mean we never call maybeMerge implicitly? (Ie, neither on close nor NRT reader or any other time), rather than just singling out updateDocument/addDocument? Eg if we add other methods in the future (like field updates), it should also prevent those from doing merges? > Add setting that prevents merging on updateDocument > --------------------------------------------------- > > Key: LUCENE-4472 > URL: https://issues.apache.org/jira/browse/LUCENE-4472 > Project: Lucene - Core > Issue Type: Improvement > Components: core/index > Affects Versions: 4.0 > Reporter: Simon Willnauer > Fix For: 4.1, 5.0 > > Attachments: LUCENE-4472.patch > > > Currently we always call maybeMerge if a segment was flushed after updateDocument. Some apps and in particular ElasticSearch uses some hacky workarounds to disable that ie for merge throttling. It should be easier to enable this kind of behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org