Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5989

Use DC.keyEquivalence().hashCode() for hashing into segments

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Obsolete
    • Major
    • 9.0.0.Beta1
    • 8.1.0.Beta1
    • Core
    • None

    Description

      Custom Equivalence is not taken into account in key -> segment decision.

      This is also related to ISPN-3905, the fix should remove the expensive string encoding as well.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-3905 Murmurhash3 implementation is slow on String keys

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rvansa1@redhat.com Radim Vansa (Inactive)
              rvansa1@redhat.com Radim Vansa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: