Skip to content

Three keys, very strange hash #1

@PlkMarudny

Description

@PlkMarudny

Trying to create the hash with the following keys (NewHashMap(16))

SCENE*CHANNELS/AlArabiya/NEWS/N_Strap/BG_N_Strap
SCENE*CHANNELS/AlArabiya/NEWS/N_Strap/BG_N_Strap
SCENE*CHANNELS/AlArabiya/SHOWS/MorningShow_2015/SCENES/STRAPS/BG_N_Headlines_MS

What I am getting, is only one bucket with the last value (SCENE*CHANNELS/AlArabiya/SHOWS/MorningShow_2015/SCENES/STRAPS/BG_N_Headlines_MS, hash key 15676253695511815426) and two chained values from the above (hash 12974028310590649090).
I would expect two buckets, one with the hash 15676253695511815426, and another bucket with hash 12974028310590649090 and chained the second item. Is this an expected behaviour? Shouldn't the number of buckets be increased when a mapping collision like above happens?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions