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] Created: (MRM-1293) migrate repository statistics to the
metadata content repository
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
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
[jira] Assigned: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1293:
----------------------------------
Fix Version/s: (was: 1.3)
1.3.1
> 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
> Fix For: 1.3.1
>
>
> 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
[jira] Updated: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1293:
------------------------------
Fix Version/s: 1.3
> 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
> Fix For: 1.3
>
>
> 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
[jira] Commented: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201632#action_201632 ]
Brett Porter commented on MRM-1293:
-----------------------------------
have started to commit this implementation to the MRM-1025 branch. Currently only the last bullet point remains to be implemented, as well as to re-add the storage of extended statistics (artifact counts), then to clean up the old beans.
> 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
> Fix For: 1.3
>
>
> 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
[jira] Closed: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1293.
-----------------------------
Resolution: Fixed
> 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
> Fix For: 1.4
>
>
> 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
[jira] Commented: (MRM-1293) migrate repository statistics to the
metadata content repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201725#action_201725 ]
Brett Porter commented on MRM-1293:
-----------------------------------
the main portion of work is now done. However, it is not currently doing the total artifact counts that were done from the database. This needs to be revisited before closing the issue
> 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
> Fix For: 1.3
>
>
> 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