Actions
Idea #15093
closed
Work with Ops to decide best DB migration strategy for collection file count & size
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
Due date:
Story points:
-
Updated by Tom Morris almost 6 years ago
- Related to Idea #14484: [API Server] Return collection size and number of files in collection record added
Updated by Tom Morris almost 6 years ago
- Status changed from In Progress to New
- Assigned To deleted (
Eric Biagiotti) - Target version changed from 2019-04-24 Sprint to To Be Groomed
Updated by Tom Morris over 5 years ago
- Blocked by Idea #15180: [Spike] Test migration on production database added
Updated by Ward Vandewege over 5 years ago
- Category set to API
- Status changed from New to In Progress
- Assigned To set to Ward Vandewege
- Target version changed from To Be Groomed to 2019-06-05 Sprint
Updated by Ward Vandewege over 5 years ago
15093-move-collection-update-out-of-band up for review at 0d8adf9bb22e169fb47d64ca19045283ff5fafd1
Updated by Eric Biagiotti over 5 years ago
Ward Vandewege wrote:
15093-move-collection-update-out-of-band up for review at 0d8adf9bb22e169fb47d64ca19045283ff5fafd1
Just a minor note. Because of the addition of the file_count=0 in the where clause, the distinct_pdh_count query could potentially return a number greater than the total number of pdhs processed and the logging in group_pdhs_for_multiple_transactions would be inaccurate. This doesn't affect actual collection processing though. Could just add the same where clause to distinct_pdh_count query.
Otherwise, this LGTM.
Updated by Ward Vandewege over 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|d7775a8a4f85771a4bf2ac6165561f0d4393060a.
Actions