Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-12367

Document search loads person record for each row needlessly.

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Similar issues:
      KULRICE-7744MAINTENANCE: New person record stuck in ENROUTE status
      KULRICE-5494Select control in a collectiongroup should be able to use different data for each row
      KULRICE-13476Create script to bulk load Component documents with pending Approval
      KULRICE-13530Loadtest bulk data: Load 1000 users with 100 action requests each
      KULRICE-8836Person maintenance screen loading very slowly when the person has a lot of roles
      KULRICE-9165Person document not displaying role qualifiers
      KULRICE-3662Message Properties aren't getting loaded from KEW ApplicationResources.properties for KEW lookup screens (like doc search)
      KULRICE-5901MySQL sequence generation is resulting in a new row in the sequence table for each value retrieved
      KULRICE-8337Adding line to group membership on person record causes NPE
      KULRICE-4601Query to KREW_RIA_DOCTYPE_MAP_T happening for each search result row
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Contributing Institution:
      Indiana Univ
    • Include in Release Notes?:
      Yes

      Description

      When the DocumentSearchCriteriaBoLookupableHelperService tries to generate the URL for the person inquiry it ends up going to the database to fetch the full person object. This would be fine but it fetches the person by principal ID and all it does with that person object is pull the principal ID from it. This leads to up to 300-400ms of extra overhead per unique person in the document search results to fetch the person object since it is so slow to get it from the database for information it already had. Making this simple change drastically increases the performance of the document search screen.

        Activity

        Hide
        Shravya Saripella (Inactive) added a comment -

        Contribution complete

        Show
        Shravya Saripella (Inactive) added a comment - Contribution complete
        Hide
        Jessica Coltrin (Inactive) added a comment -

        moving IU contributions to 2.5

        Show
        Jessica Coltrin (Inactive) added a comment - moving IU contributions to 2.5

          People

          • Assignee:
            Unassigned
            Reporter:
            James Bennett
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel