Github user rednaxelafx commented on the issue:
https://github.com/apache/spark/pull/21643
https://github.com/apache/spark/pull/21643#pullrequestreview-131977512
For all practical purposes, no, this change shouldn't break any use cases
that we support; there could be use cases that we didn't intend to support that
might break.
In Spark SQL, SQL/DataFrame/Dataset operations are all type-checked, and
the analyzer will strictly reject operations that involve incompatible types.
Array types in Spark SQL are neither covariant nor contravariant, so e.g.
`array<int>` and `array<long>` would be considered incompatible, and the
analyzer would have rejected equality comparison between them in the first
place.
In all other cases, `GenericArrayData` is a Spark SQL internal type that
shouldn't be used on the outside, and I don't think we ever intended to support
direct access of this type from the outside.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
