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

Kim Attribute problem when multiple attributes have the same name

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical 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
    • Similar issues:
      KULRICE-12100KIM Attributes are referenced by a non-unique identifier
      KULRICE-1470KIM Qualified Role with multiple qualifications
      KULRICE-3455Possible issues with remoting of KIM Type Services and attributes
      KULRICE-3532Include description attribute on all tag library attributes
      KULRICE-7986Problems with multiple refreshWhenChangedPropertyNames
      KULRICE-13173KIM Group attributes does not persist.
      KULRICE-5356Create a Servlet Filter to check for session attributes that are
      KULRICE-13248Error on group lookup when searching by KIM type on groups with attributes
      KULRICE-4516KimDocumentRoleMemberLookupableHelperServiceImpl confused by multiple docs
      KULRICE-11549Conversion Script- When tranforming MaintainableFieldDefinition, the name attribute is the only one being transformed.
    • 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.

        Issue Links

          Activity

          Hide
          Gayathri Athreya added a comment -

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

          Show
          Gayathri Athreya added a comment - Kristina, the patch you added is what Jeremy attached right? Or are there changes to it?
          Hide
          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
          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
          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
          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
          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
          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
          Gayathri Athreya added a comment -

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

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

            People

            • Assignee:
              Gayathri Athreya
              Reporter:
              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

                  Agile

                    Structure Helper Panel