I eventually decided to keep them in 1.6.1 because they are important changes and the current array-style output is really troublesome. Considering the raster functions are still fast evolving, so maybe it is fine to keep them in a maintenance release?
On Tue, Aug 20, 2024 at 7:53 PM Kristin Cowalcijk <kontinuat...@apache.org> wrote: > > I've noticed that breaking changes SEDONA-629 > (https://github.com/apache/sedona/pull/1524) and SEDONA-633 > (https://github.com/apache/sedona/pull/1539) are included in this > release, is this expected or do we have to exclude them from 1.6.1 and > release them in 1.7.0? > > SEDONA-607 (https://github.com/apache/sedona/pull/1525/files) is not > working as expected, the following query raises an exception, but the > error message does not have the problematic geometry included: > > ``` > >>> sedona.range(0, 10).selectExpr("ST_Buffer(ST_Point(id, id), 1) > >>> buf").selectExpr("ST_MakeLine(buf, buf)").show() > > 24/08/21 02:42:05 ERROR Executor: Exception in task 0.0 in stage 7.0 (TID 7) > org.apache.spark.sql.sedona_sql.expressions.InferredExpressionException: > Exception occurred while evaluating expression - source: [], cause: > ST_MakeLine only supports Point, MultiPoint and LineString geometries > ```
