Uploaded image for project: 'mod-search'
  1. mod-search
  2. MSEARCH-337

Gracefully handle 500 error on the wildcard search on large data set

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 1.7.0
    • None
    • Falcon Sprint 138
    • 0.5
    • Falcon
    • TBD

    Description

      Overview:
      Steps to Reproduce:
      Log into https://pre-lotus-cap1.int.aws.folio.org/
      Reach out to PTF for credentials
      Request

      curl --location --request GET 'https://okapi-lcp1-us-east-1.int.aws.folio.org/search/instances?query=keyword all "*fusion pepper*"&limit=100' \
      --header 'x-okapi-tenant: fs09000000' \
      --header 'x-okapi-token: "${XOKAPITOKEN}"' \
      --header 'Content-Type: application/json'
      

      Response:

      HTTP 500 Internal Server Error.
      If the issue persists, please report it to EBSCO Connect.
      

      This happens when the search does not find any record. 500 is misleading because the Server was not down.

      I was also able to recreate in Lotus Bugfest.

      Expected Results:
      Return HTTP status 200

      {"totalRecords":0,"instances":[]}
      

      Actual Results:

      HTTP 500 Internal Server Error.
      If the issue persists, please report it to EBSCO Connect.
      

      Additional Information
      A similar query works fine in a snapshot environment. 500 in the above environments(PTF and Lotus Bugfest) is mostly due to large data volume.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                pavel_filippov Pavel Filippov
                varunjavalkar Varun Javalkar
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases