Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.6.0
Description
This issue is similar to SEDONA-20. We have encountered errors caused by this when working with datasets aggregated using RS_Union_Aggr. The ExpressionEncoder will create new instances of registered UserDefinedType classes, so we have to make sure that such newly created instances are the same type as the RasterUDT case object, otherwise we'll see strange SQL analyze exceptions and type mismatches.
We also found that the implementation of GeometryUDT.hashCode is not correct: objects that are equal with each other has different hash values. Although this is not causing problems for now but we'd better fix it.
Attachments
Issue Links
- links to