Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/5065
Hmm, I agree with @twalthr. Adding these checks when a DataSet/DataStream
is imported would prevent valid queries (e.g., those that to simple
transformations). I would not add a config switch to disable the global checks.
Adding the checks to the operators that require properly implemented `equals()`
and `hashCode()` methods sounds like a better approach.
We should also add to the documentation that all objects that are processed
by the Table API / SQL should have equals and hashCode properly implemented.
---
