Search results

Wrong nullability handling for coalesce

Status: Open.

#951 In substrait-io/substrait;

· vbarua opened on Jan 29, 2026

Formally specify type parameter semantics

Status: Open.

#948 In substrait-io/substrait;

· benbellick opened on Jan 28, 2026

pixi-fy substrait repo tooling

Status: Open.

#946 In substrait-io/substrait;

· nielspardon opened on Jan 28, 2026

Handling of unsigned numeric types

Status: Open.

#944 In substrait-io/substrait;

· kadinrabo opened on Jan 27, 2026

Clarify whether <code>any[\d]</code> type parameters can bind arguments with differing outermost nullability

Status: Open.

#943 In substrait-io/substrait;

· benbellick opened on Jan 26, 2026

Clarify type equality definition

Status: Open.

#941 In substrait-io/substrait;

· benbellick opened on Jan 26, 2026

Require function names to be unique within extension YAML files

Status: Open.

#931 In substrait-io/substrait;

· benbellick opened on Jan 7, 2026

RANGE bounds spec is overly restrictive for UNBOUNDED/CURRENT ROW

Status: Open.

#930 In substrait-io/substrait;

· asolimando opened on Jan 7, 2026

clarify default behavior of <code>parameterConsistency</code> or require parameter

Status: Open.

#928 In substrait-io/substrait;

· benbellick opened on Jan 7, 2026

Timestamp and interval precision synchronization

Status: Open.

#926 In substrait-io/substrait;

· kadinrabo opened on Dec 30, 2025

Automate Substrait Artifact Generation

Status: Open.

#925 In substrait-io/substrait;

· vbarua opened on Dec 29, 2025

docs: clarify nullable-ness of string representation of UDT structure

Status: Open.

#920 In substrait-io/substrait;

· benbellick opened on Dec 17, 2025