Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12021

Kim Attribute problem when multiple attributes have the same name

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.5, 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KIM
    • Application Requirement:
      KPME
    • Sprint:
      2.4.0-rc1 Sprint 5, 2.4.0-rc1 Sprint 7, 2.4.0-rc1 Sprint 8
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      We've found an issue where getting memberships for a role isn't working even when wildcarding the qualifiers because there are two KimAttributes in the database with the same attributeName.

      The attributes have different namespaces, and are linked with different Kim Types, but it seems like queries in KimRoleBase are getting the attribute by getting the first attribute with that attributeName, and then returning the first record returned.

        Attachments

          Issue Links

            Activity

            Hide
            gathreya Gayathri Athreya added a comment -

            Kristina, the patch you added is what Jeremy attached right? Or are there changes to it?

            Show
            gathreya Gayathri Athreya added a comment - Kristina, the patch you added is what Jeremy attached right? Or are there changes to it?
            Hide
            kbtaylor Kristina Taylor (Inactive) added a comment - - edited

            No, because of the KTI discussion, the implementation that was applied was slightly different, but Jeremy checked it and said it would work for him.

            Show
            kbtaylor Kristina Taylor (Inactive) added a comment - - edited No, because of the KTI discussion, the implementation that was applied was slightly different, but Jeremy checked it and said it would work for him.
            Hide
            kbtaylor Kristina Taylor (Inactive) added a comment -

            The integration tests discovered some bugs with my implementation. I have committed the fixes to the 2.3 branch before the merge to 2.4.

            Show
            kbtaylor Kristina Taylor (Inactive) added a comment - The integration tests discovered some bugs with my implementation. I have committed the fixes to the 2.3 branch before the merge to 2.4.
            Hide
            kbtaylor Kristina Taylor (Inactive) added a comment -

            Tests are now passing in CI, so I will mark this as resolved for 2.3. 2.4 will get the changes as a result of the weekly merge.

            Show
            kbtaylor Kristina Taylor (Inactive) added a comment - Tests are now passing in CI, so I will mark this as resolved for 2.3. 2.4 will get the changes as a result of the weekly merge.
            Hide
            gathreya Gayathri Athreya added a comment -

            Reopening since KC is having trouble with this patch. Details will be mentioned in the crucible review.

            Show
            gathreya Gayathri Athreya added a comment - Reopening since KC is having trouble with this patch. Details will be mentioned in the crucible review.

              People

              • Assignee:
                gathreya Gayathri Athreya
                Reporter:
                jjhanso Jeremy Hanson
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day, 5 hours
                  1d 5h
                  Remaining:
                  Time Spent - 4 hours Remaining Estimate - 1 hour
                  1h
                  Logged:
                  Time Spent - 4 hours Remaining Estimate - 1 hour Time Not Required
                  4h