Uploaded image for project: 'mod-inventory-storage'
  1. mod-inventory-storage
  2. MODINVSTOR-468

hitcount related issues in Q1

    XMLWordPrintable

Details

    • CP: sprint 86, CP: sprint 87, CP: sprint 85
    • 8
    • Core: Platform

    Description

      Bug Context

      A number of issues have been raised in UI inventory relating to inconsistent record counts reported when searching.

      This issues in intended to cover issues found in:

      UIIN-1046 - Sorting seems to impact the record counts returned by the API
      UIIN-1049 - Effective location filter gives inconsistent record counts
      UIIN-1050 - 1000 records reported for instances suppressed from discovery, when there should be over 7000
      UIIN-1055 - Keyword search gives inconsistent record counts
      UIIN-1046 is included because it appears from testing Zak_Burke did that adding a sort clause increases the liklihood of an inaccurate record count being returned.

      Maybe this is a known limitation of the record count estimation, that cannot be easily resolved. If so, I think we need to document it in a way that can be explained to end users.

      Issues to be addressed

      • consistency in reporting hitcounts — the hitcount is an estimate but is reported consistently when using different sort and filter criteria
      • adding a dedicated function (e.g a `…`sign next to the hit count) to allow the user to retrieve a precise hit count — it is expected that this will take minutes for very large result sets (millions of record)
      • make the estimate appear less “falsely precise” — eg 18000 instead of 18245 but not commit to provide a true lower-bound for the count

      Implementation context

      Hitcount estimation is done through a nessacity – it's not possible to provide precise hitcounts in the fulltext search scenarios for result sets of millions of records.

      As explained by Adam on MODINVSTOR-321:

      There are three cases:

      1. sort by title: Using a special "optimized SQL path". If the limit is X and there are more than X records, it returns 999999999. That's of course a very weird way to return hit counts. This path AFAIK is only used by /instance-storage/instances

      2. Not sort by title and using a criteria / filter .. The hit count is an estimate if there are more than 1000 records. RMB-506

      3. Not sort by title and not using critiera/ / filter. Hit count should be accurate.

      We discussed adding functionality in RMB to allow the client to request a precise hitcount: RMB-578 and RMB-579

      This functionality ONLY makes sense in a specific circumstances (e.g user requesting precise hitcount AFTER issuing a search) not as a general replacement.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1049 Paused due to POC of Elastic Search. Bugfest: Inventory. Effective Location Result Counts Don't Add Up (Off by Unacceptable Amount) And Seem Suspicious

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1050 Paused due to POC of Elastic Search. SPIKE: Bugfest: Inventory. Item segment. Filtering on Suppress from discovery: Yes and No Don't Add Up (Off by Unacceptable Amount)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1055 Bugfest: Inventory. Sorting by Title gives different result counts than no sort when *searching*

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1070 Paused due to POC of Elastic Search. BugFest: Inventory. Search for Term and Filter by Status = Available Always Results in 1,000 Results

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1129 SPIKE: JTST Environment. Inventory. Search for Status = Available, Sort by Contributor Gives No Results in Main Pane Despite Result Count of 93,717

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            duplicates

            Bug - A problem which impairs or prevents the functions of the product. FOLIO-2557 hitcount estimation is way off

            • TBD - To be determined
            • Closed
            is blocked by

            Task - A task that needs to be done. RMB-591 remove or harmonize 'optimizedSql' execution path

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. RMB-592 SPIKE: propose improvements to the hit count estimation function

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. MODINVSTOR-467 Inconsistent Record Counts when Searching

            • TBD - To be determined
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. MODINVSTOR-321 999 999 999 Records found

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests RMB-578 Inform whether totalRecords is exact or an estimate

            • P2 - normal priority level, must be included in the current development cycle
            • Blocked

            New Feature - New feature requests RMB-579 In a GET request, control whether the server may estimate the hit count

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. RMB-592 SPIKE: propose improvements to the hit count estimation function

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2623 Wait for POC of Elastic Search - Round estimated search result hit count (totalRecords)

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CHAL-294 Query request where offset value > totalRecords returns 0 reords even if actual number of records > totalRecords

            • TBD - To be determined
            • In Code Review

            Bug - A problem which impairs or prevents the functions of the product. CIRCSTORE-210 Requests -Filtering by Request Type returns (Total Records = 1000) when there are more

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. FOLIO-2557 hitcount estimation is way off

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODINVSTOR-465 Bulk download Instance UUIDs OOM

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1071 Bugfest: Inventory. Sorting by Title gives different result counts when *filtering* ("More than 10,000 records found" (approximation is not close enough))

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                mikhail.fokanov Mikhail Fokanov
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases