Hi,

I'm assuming it's just a workaround for changing fields. The string
representation happens to be stable while the underlying values change.

It's best practice to use completely immutable types if you have similar
issues, you should double-check that nothing can be changed in your data
type or you make defensive copies before changing.

On Wed, May 5, 2021 at 4:02 PM tuk <subharaj.ma...@gmail.com> wrote:

> Can some provide a bit more explanation why replacing
> /com.google.common.base.Objects.hashCode with toString().hashCode(),/ with
> /toString().hashCode()/ making it work?
>
>
>
> --
> Sent from:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
>

Reply via email to