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

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

XMLWordPrintable

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

      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.

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

              Created:
              Updated:
              Resolved: