Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: 1.0-alpha-1
-
Component/s: repository scanning
-
Labels:None
-
Number of attachments :
Description
currently, the "last discovered" timestamp for an operation is set to the current time. There are two problems with that:
- artifacts added in the last minute are not discovered, and because of this setting never will be
- artifacts added with timestamps in the past (eg, using rsync) will never be discovered.
For the first, the time recorded can simply be set in the past.
However, for the second another alternative needs to be found (whether it be querying the target to check if it already exists or not rather than a single timestamp, or some other solution)
Issue Links
| This issue relates to: | ||||
| MRM-134 | ability to update an existing index without relying on timestamp |
|
|
|
| This issue is related to: | ||||
| MRM-37 | discover the deletion of artifacts |
|
|
|
| MRM-129 | flush the index periodically during rebuild |
|
|
|
| MRM-40 | associate artifacts with their pom and checksums |
|
|
|
| This issue is superceded by: | ||||
| MRM-134 | ability to update an existing index without relying on timestamp |
|
|
|