Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-21017

Add an API to recompute quota for Tenant or User

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 9.10-HF01, 10.1
    • Component/s: Quotas
    • Release Notes Summary:
      New API to recompute quota for tenant or user
    • Backlog priority:
      1,500
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      New operation: Quotas.RecomputeStatistics, with optional parameters:

      • tenantId / username / path (only one allowed)
      • updaterName (defaults to documentsSizeUpdater)
      Show
      New operation: Quotas.RecomputeStatistics , with optional parameters: tenantId / username / path (only one allowed) updaterName (defaults to documentsSizeUpdater )
    • Sprint:
      nxcore 9.10.2, nxcore 10.1.1
    • Story Points:
      3

      Description

      In Nuxeo (nuxeo-quota-core), quota re-computation can be done only for entire repository and there is no API to compute quota based on Tenant and User.
      Need to add a method in QuotaStatsService and QuotaStatsUpdater with slight modifications in quota-core classes to achieve this.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.