lucene-dev mailing list archives

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


Robert Muir commented on LUCENE-4746:

No matter what moveIndexes will be unsafe right? Meaning if you hit an exc part way through
then some or all of your source indices are corrupt ... the dest index should be fine though
(and, should only reflect all or none of the additions I think).

Yeah at least i think it has to be. even if added complex crap and tried to move files back
etc, someone could run out of disk space during the process or all kinds of other possibilities.

I think in general speeding up addIndexes to be more efficient (and still safe) is most attractive.
But i know some systems cant support hard linking so i think it would be good to have a more
generally fast method for them. Maybe there is a way it wouldnt have to be on indexwriter
as well (but a tool in contrib), i dont know.
> 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