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 2009/12/02 14:27:55 UTC
[jira] Assigned: (MRM-1293) migrate repository statistics to the
metadata content repository
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reassigned MRM-1293:
---------------------------------
Assignee: Brett Porter
> migrate repository statistics to the metadata content repository
> ----------------------------------------------------------------
>
> Key: MRM-1293
> URL: http://jira.codehaus.org/browse/MRM-1293
> Project: Archiva
> Issue Type: Improvement
> Reporter: Brett Porter
> Assignee: Brett Porter
>
> currently, after every scan, repository statistics are persisted to the database. These could easily be stored in the metadata repository. While at present we will keep the "per-scan" approach, in the future this might better be represented as a regularly stored snapshot / built in versioning of the metadata. It could potentially be adding this information on the fly instead of at scan by adding a callback in the repository API when an artifact / project is created - however this will be approached later.
> When migrating the functionality, it should be offered as a standalone plugin (the only dependencies should be in the webapp that need to render the information and trigger some cleanup).
> The following changes will be needed:
> - save the statistics in ArchivaRepositoryScanningTaskExecutor / ArchivaRepositoryScanningTaskExecutorTest
> - reset statistics in EditManagedRepositoryAction / EditManagedRepositoryActionTest when location changes
> - query for a prior successful scan in RepositoryArchivaTaskScheduler
> - retrieve last scan info in RepositoryAction and update corresponding JSP to display information correctly
> - generate report action to query scan statistics between given dates and aggregate
--
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