Releases: substrait-io/substrait
Releases · substrait-io/substrait
v0.45.0
0.45.0 (2024-03-24)
Features
- add decimal type support for sum0 function (#610) (6bd0c7b)
v0.44.0
0.44.0 (2024-03-03)
⚠ BREAKING CHANGES
- Adding a NULL option to the on_domain_errors.
SQLite returns null for some inputs such as negative infinity
Features
- add extra option for on domain errors in log functions (#536) (cbec079)
- add ignore nulls options to concat function (#605) (55db05b)
v0.43.0
0.43.0 (2024-02-25)
Features
- include precision parameter in timestamp types (#594) (087f87c)
Bug Fixes
- remove function definitions w/ invalid return types (#599) (a3b1f32)
v0.42.1
0.42.1 (2024-01-28)
Bug Fixes
- add missing RelCommon field to WriteRel and DdlRel (#591) (d55703a)
v0.41.0
0.41.0 (2023-12-24)
⚠ BREAKING CHANGES
- Renamed modulus to modulo.
Added options and documentation for the modulo operator as defined in
math and comp sci.
Bug Fixes
- renamed modulus to modulo; updated modulo operator defintion (#583) (aba1bc7), closes #353
v0.40.0
0.40.0 (2023-12-17)
⚠ BREAKING CHANGES
- The enum
WriteRel::OutputMode
had an option change
from
OUTPUT_MODE_MODIFIED_TUPLES
to OUTPUT_MODE_MODIFIED_RECORDS
- The message
AggregateFunction.ReferenceRel
has moved
to ReferenceRel
.
Features
v0.39.0
0.39.0 (2023-11-26)
⚠ BREAKING CHANGES
-
- Map keys may be repeated.
- Map keys must not be NULL.
- The map key type may be nullable.
This is based on the current restrictions found in the wild.
DuckDB, Velox, Spark, and Acero all reject attempts to provide NULL as a
key.
Despite DuckDB specifically calling out that keys must be unique in its
implementation other implementations such as Velox and Acero do not
require the key to be unique so we cannot require the map key to be 1:1
with map values.
Features
- support for simple extensions dependencies (#265) (f0ecf54)
Documentation
v0.38.0
0.38.0 (2023-11-05)
Features
- add least and greatest functions to functions_comparison.yml (#247) (b3071bc)