Uploaded image for project: 'Gateway'
  1. Gateway
  2. GTWY-1271

Metrics filters need to require new transactions and precisely delinate scope

XMLWordPrintable

    • Icon: Defect Defect
    • Resolution: Done
    • Icon: Critical Critical
    • 1.0.0-RC3
    • 1.0.0-BETA2
    • None
    • None

      Currently the metrics filters define a writable transaction around the whole request scope. This is causing a number of problems. One of the core problems is that now all read-only operations can potentially write accidental changes, as well potentially very expensive dirty checks as part of the final flush. This particular problem manifests itself in file listing pages, datasets with many nest collections etc.

      We may also want to review combining the multiple filters into single filter to reduce the transactional overhead. We would still want to separate the functional components but may need to wrap in under a single transaction.

              nhook Nathan Hook
              wilhelmi Nathan Wilhelmi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: