lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4746) Create a move method in Directory.
Date Sat, 02 Feb 2013 15:54:12 GMT


Robert Muir updated LUCENE-4746:

    Attachment: LUCENE-4746.patch

here's a prototype.

My main concerns are:
* 3.0 formatted indexes with shared doc stores. We shouldnt support this. throwing exception
when we see it makes the method more dangerous / doing an extra-pass to detect it = unacceptable
(this is the kind of hairiness we must avoid).
* I dont want a slow (but safe) addIndexes and a fast (but unsafe) moveIndexes. So if we do
this, i want java7 as a minimum requirement so we can at least try to create a hard link in
Directory.copy() to make addIndexes fast too. 

To me, these both suggest trunk-only, but i'm open to other ideas. 
> Create a move method in Directory.
> ----------------------------------
>                 Key: LUCENE-4746
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.2, 5.0
>         Attachments: LUCENE-4746.patch
> I'd like to make a move method for directory.
> We already have a move for Solr in DirectoryFactory, but it seems it belongs at the directory
level really.
> The default impl can do a copy and delete, but most implementations will be able to optimize
to a rename.
> Besides the move we do for Solr (to move a replicated index into place), it would also
be useful for another feature I'd like to add - the ability to merge an index with moves rather
than copies. In some cases, you don't need/want to copy all the files and could just rename/move

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message