Venki Korukanti

Looking at the invariant enforcement code [here](https://github.com/delta-io/delta/blob/master/core/src/main/scala/org/apache/spark/sql/delta/constraints/Invariants.scala#L79), it looks like if the column is not nullable, the invariant by `delta.invariants` is not considered at all. The existing test has `nullable=true`...

The expression needs to be in JSON format. In the example test this is the input `{"delta.invariants":"{\"expression\":{\"expression\":\"value < 3\"}}"}`

@wjones127 Heard from @zsxwing that this feature has bugs and is being deprecated in favor of the [constraints](https://docs.delta.io/latest/delta-constraints.html).

Closing this issue. @wjones127.

@wjones127 Makes sense. Reopening. Not sure what is the procedure to deprecate the features. @tdas?

@felipepessoto No, I am not planning to implement. @zsxwing assigned it to me to look at it and provide any guidance. We are currently busy with the next release of...

> @koconder - after discussing with another engineer @vkorukanti on my team, this PR is a little bit too big to review. Could you split this up into, say, 2...

Hi @dwsmith1983, thanks for the question. There is no particular reason why we map null to 0. Currently the Z-Order used Spark's RangePartitioner to map the Z-Order column to a...

@Dearkano Thanks for reporting the issue. Is it possible to share the Trino query execution profile _before optimize_ and _after optimize_ for one of the TPCDS queries (preferably Q21 which...

@Dearkano do you have the same problem on your production data? Wondering have you tried changing the max split size in Trino?