general contract for hashCodesays
This integer should not remain consistent with one execution of the application on another execution of the same application.
So, for something like Spark, which has separate JVMs for each artist, does it do anything to ensure that the hash codes are consistent in the cluster?
In my experience, I use things with deterministic hashes, so this was not a problem.
source
share