Package com.carrotsearch.hppc
Class HashOrderMixing
java.lang.Object
com.carrotsearch.hppc.HashOrderMixing
Factory methods to acquire the most common types of
HashOrderMixingStrategy
.- See Also:
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionprivate static final HashOrderMixingStrategy
static final String
private static HashOrderMixing.Strategy
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic HashOrderMixingStrategy
constant
(long seed) A constantHashOrderMixingStrategy
.static HashOrderMixingStrategy
Returns the currently configured defaultHashOrderMixingStrategy
.static HashOrderMixingStrategy
Deprecated.Permanently deprecated as a warning signal.static HashOrderMixingStrategy
none()
Deprecated.Permanently deprecated as a warning signal.static HashOrderMixingStrategy
Returns a randomizedHashOrderMixingStrategy
that issues unique per-container seed.
-
Field Details
-
PROPERTY_BIT_MIXER
- See Also:
-
strategy
-
DETERMINISTIC
- See Also:
-
-
Constructor Details
-
HashOrderMixing
private HashOrderMixing()
-
-
Method Details
-
randomized
Returns a randomizedHashOrderMixingStrategy
that issues unique per-container seed. This minimizes the chances of hash distribution conflicts. -
constant
A constantHashOrderMixingStrategy
. This is useful if one needs to have deterministic key distribution but wishes to control it manually. Do not use the same constant for more than one container. Consider using scatter maps or sets instead of constant hash order mixer. -
deterministic
Deprecated.Permanently deprecated as a warning signal.DeterministicHashOrderMixingStrategy
will reorder keys depending on the size of the container's buffer. This is inherently unsafe with hash containers using linear conflict addressing. The only use case when this can be useful is to count/ collect unique keys (for which scatter tables should be used). -
none
Deprecated.Permanently deprecated as a warning signal.This strategy does not change the hash order of keys at all. This is inherently unsafe with hash containers using linear conflict addressing. The only use case when this can be useful is to count/ collect unique keys (for which scatter tables should be used). -
defaultStrategy
Returns the currently configured defaultHashOrderMixingStrategy
.
-