You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/08/02 07:17:31 UTC
[jira] Created: (MRM-134) ability to update an existing index
without relying on timestamp
ability to update an existing index without relying on timestamp
----------------------------------------------------------------
Key: MRM-134
URL: http://jira.codehaus.org/browse/MRM-134
Project: Maven Repository Manager
Issue Type: Improvement
Components: indexing
Reporter: Brett Porter
Fix For: 1.0-beta-1
due to the possibility that timestamps can get out of sync, it should be possible to update an index without relying on these in a performant way (ie, not rebuilding from scratch).
for example, compare the artifact timestamp to the target location before deciding if an addition/update is needed and reading the JAR (possibly the slowest part of indexing - should confirm what % it takes)
this will also need to process deletions (which may not be handled in the normal indexing, depending on how that is implemented for discovery)
--
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-134) ability to update an existing index
without relying on timestamp
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-134?page=all ]
Brett Porter closed MRM-134.
----------------------------
Assignee: Brett Porter
Resolution: Fixed
done, though:
- no timestamp checking at present (can be added in a later iteration, but should be unnecessary for basic purposes as indexed files shouldn't be updated)
- no deletion (this will be addressed by the separate JIRA issue for it)
> ability to update an existing index without relying on timestamp
> ----------------------------------------------------------------
>
> Key: MRM-134
> URL: http://jira.codehaus.org/browse/MRM-134
> Project: Archiva
> Issue Type: Improvement
> Components: indexing
> Reporter: Brett Porter
> Assigned To: Brett Porter
> Fix For: 1.0-beta-1
>
>
> due to the possibility that timestamps can get out of sync, it should be possible to update an index without relying on these in a performant way (ie, not rebuilding from scratch).
> for example, compare the artifact timestamp to the target location before deciding if an addition/update is needed and reading the JAR (possibly the slowest part of indexing - should confirm what % it takes)
> this will also need to process deletions (which may not be handled in the normal indexing, depending on how that is implemented for discovery)
--
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-134) ability to update an existing index
without relying on timestamp
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-134?page=all ]
Brett Porter updated MRM-134:
-----------------------------
Fix Version/s: 1.0-beta-1
> ability to update an existing index without relying on timestamp
> ----------------------------------------------------------------
>
> Key: MRM-134
> URL: http://jira.codehaus.org/browse/MRM-134
> Project: Maven Repository Manager
> Issue Type: Improvement
> Components: indexing
> Reporter: Brett Porter
> Fix For: 1.0-beta-1
>
>
> due to the possibility that timestamps can get out of sync, it should be possible to update an index without relying on these in a performant way (ie, not rebuilding from scratch).
> for example, compare the artifact timestamp to the target location before deciding if an addition/update is needed and reading the JAR (possibly the slowest part of indexing - should confirm what % it takes)
> this will also need to process deletions (which may not be handled in the normal indexing, depending on how that is implemented for discovery)
--
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