Hi all,
I ran into an issue using the REST scan planning APIs where filters
containing the boolean expressions were failing to be parsed. The REST spec
defines these models as an object wrapping the string representation like
{"type": "true"}, but the ExpressionParser actually read and writes them as
plain booleans. That mismatch causes the parser to reject filters that
follow the current spec.
I opened a PR to update the REST spec to align with how the expression
parser is used.
If anyone has any concerns with the spec change, or thinks we should handle
it differently (for example by changing the Java representation instead),
I’d appreciate any feedback.
PR: https://github.com/apache/iceberg/pull/14677
- Drew
