Uploaded image for project: 'MidPoint'
  1. MidPoint
  2. MID-6558

Pre-processing of collection objects as input for reports to limit OOMs and resource fetch

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.2
    • Fix Version/s: 4.4
    • Component/s: Reporting
    • Labels:
    • Subscription:
      Active subscription

      Description

      Objects which should be evaluated in the report "Column > Export" section should originate rather from some "pre-processing" section than the filtered collection. The pre processing would take the object from the collection as an input, potentially make additional filtering and return a modified object.

      Example: Collection returns a raw shadow from the repository, pre-processing filters the shadows based on the owner attributes and after that a full shadow is pulled and returned from pre processing for further evaluation in the "Condition" an later "Column > Export" section.

      This would limit fetches from the resource and also help with heap consumption (Collection listing shadows with noFetch=false )  

        Attachments

          Activity

            People

            Assignee:
            mmacik Matus Macik
            Reporter:
            mmacik Matus Macik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: