Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3.0
-
Fix Version/s: 3.15.0
-
Component/s: Database OrientDB
-
Story Points:8
-
Epic Link:
Description
We renamed the last_accessed field to last_downloaded as part of the work on NEXUS-12360, but the existing semantics don't entirely match what one would expect given the rename. In particular, there are a few situations where the Last Downloaded timestamp is updated when content is uploaded, and this doesn't match the expectations for it not to be.
Overall there are a couple of obvious solutions:
- We can rename the field (again) to something more neutral.
- We can stop updating this field for upload operations.
Given the expectations in NEXUS-12360 and conversations since then, I'm assuming we'll want to stop updating the field for upload operations and the like.
Attachments
Issue Links
- relates
-
NEXUS-19084 Many threads blocked in Elasticsearch while updating LastDownloaded attribute
-
- Closed
-
1.
|
Add last downloaded handler for Maven |
|
Closed | Joseph Stephens |
2.
|
Add last download handler to Bower |
|
Closed | Joseph Stephens |
3.
|
Add last download handler to Docker |
|
Closed | Joseph Stephens |
4.
|
Add last download handler to npm |
|
Closed | Joseph Stephens |
5.
|
Add last download handler to Nuget |
|
Closed | Joseph Stephens |
6.
|
Add last download handler to PyPI |
|
Closed | Joseph Stephens |
7.
|
Add last download handler to Rubygems |
|
Closed | Unassigned |
8.
|
Add last download handler to Yum |
|
Closed | Moncef Ben-Soula |
9.
|
Add last download handler to Raw |
|
Closed | Jeremy Bryan |
10.
|
Move getLastDownloadedTime to RepositoryITSupport to remove duplication |
|
Closed | Joseph Stephens |