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

Make it possible to disable aggregation computations on initial search

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 9.10, 10.1
    • Fix Version/s: 10.3
    • Component/s: Web UI
    • Release Notes Summary:
      Allows search initialisation to skip aggregation for large repositories
    • Backlog priority:
      1,000
    • Upgrade notes:
      Hide

      A nuxeo search form result layout can dynamically tell whether aggregations should be computed. For instance, on the nuxeo-default-search-form.html, if aggregations should not be computed if the full text parameter is not set, you can add the following

              skipAggregates: {
                type: Boolean,
                notify: true,
                computed: '_skipAggregates(params.*)'
              }
      

      where

            _skipAggregates : function() {
              return !this.params || !this.params.ecm_fulltext || this.params.ecm_fulltext.length === 0;
            },
      
      Show
      A nuxeo search form result layout can dynamically tell whether aggregations should be computed. For instance, on the nuxeo-default-search-form.html , if aggregations should not be computed if the full text parameter is not set, you can add the following skipAggregates: { type: Boolean , notify: true , computed: '_skipAggregates(params.*)' } where _skipAggregates : function() { return ! this .params || ! this .params.ecm_fulltext || this .params.ecm_fulltext.length === 0; },
    • Sprint:
      nxGang Sprint 10.2.9, nxGang Sprint 10.3.1, nxGang Sprint 10.3.2, nxGang Sprint 10.3.3, nxGang Sprint 10.3.8
    • Story Points:
      1

      Description

      When opening the search drawer for the first time, user must wait for the first query to complete before being able to actual search for something.

      This is costly for several reasons:

      • computing aggregates on all the content of a large repository is costly and long on the elasticsearch side (30s on a 500M doc repository without user concurrency)
      • making user wait before being able to search is poor UX

      This is not the same things as disabling auto search. This issue iss only about opening the drawer for the first time after login.

      Proposed solution (Tiago)
      Allow attribute on search to disable first call, as this call server the porpose of getting ES buckets.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                3 Vote for this issue
                Watchers:
                7 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 - 3 days, 40 minutes
                  3d 40m

                    PagerDuty

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