You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Littlestar (JIRA)" <ji...@apache.org> on 2014/01/26 11:55:39 UTC
[jira] [Comment Edited] (LUCENE-5228) IndexWriter.addIndexes copies
raw files but acquires no locks
[ https://issues.apache.org/jira/browse/LUCENE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882266#comment-13882266 ]
Littlestar edited comment on LUCENE-5228 at 1/26/14 10:54 AM:
--------------------------------------------------------------
not fixed in 4.6.1? Thanks.
>>>I see stuff like: "merge problem with lucene 3 and 4 indices" (from solr users list), and cannot even think how to respond to these users because so many things can go wrong with IndexWriter.addIndexes(Directory)
may related to LUCENE-5377
was (Author: cnstar9988):
not fixed in 4.6.1? Thanks.
>>>I see stuff like: "merge problem with lucene 3 and 4 indices" (from solr users list), and cannot even think how to respond to these users because so many things can go wrong with IndexWriter.addIndexes(Directory)
may related to https://issues.apache.org/jira/browse/LUCENE-5377
> IndexWriter.addIndexes copies raw files but acquires no locks
> -------------------------------------------------------------
>
> Key: LUCENE-5228
> URL: https://issues.apache.org/jira/browse/LUCENE-5228
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Michael McCandless
> Fix For: 5.0, 4.7
>
> Attachments: LUCENE-5228.patch
>
>
> I see stuff like: "merge problem with lucene 3 and 4 indices" (from solr users list), and cannot even think how to respond to these users because so many things can go wrong with IndexWriter.addIndexes(Directory)
> it currently has in its javadocs:
> NOTE: the index in each Directory must not be changed (opened by a writer) while this method is running. This method does not acquire a write lock in each input Directory, so it is up to the caller to enforce this.
> This method should be acquiring locks: its copying *RAW FILES*. Otherwise we should remove it. If someone doesnt like that, or is mad because its 10ns slower, they can use NoLockFactory.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org