You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/07/26 05:27:26 UTC

[jira] Created: (MRM-890) make it possible to reindex / rescan without clearing database

make it possible to reindex / rescan without clearing database
--------------------------------------------------------------

                 Key: MRM-890
                 URL: http://jira.codehaus.org/browse/MRM-890
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.1
            Reporter: Brett Porter


flushing the database not only takes a long time, but it resets a number of useful attributes (such as RSS times - though this could be helped by adding artifacts with their file system timestamp), and also makes search/browse for the repo fail or be incomplete during the period. It should be possible to force a rescan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRM-890) make it possible to reindex / rescan without clearing database

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-890:
-----------------------------

    Fix Version/s: 1.2

> make it possible to reindex / rescan without clearing database
> --------------------------------------------------------------
>
>                 Key: MRM-890
>                 URL: http://jira.codehaus.org/browse/MRM-890
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Brett Porter
>             Fix For: 1.2
>
>
> flushing the database not only takes a long time, but it resets a number of useful attributes (such as RSS times - though this could be helped by adding artifacts with their file system timestamp), and also makes search/browse for the repo fail or be incomplete during the period. It should be possible to force a rescan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira