Chris Lu 9561d95507 parquet_pushdown: predicate must be a bound expression with schema id ...

Without naming a schema, a serialized predicate's column references
are ambiguous: the same field name can refer to different field IDs
across schema-evolution events, and Substrait field-reference IDs
mean nothing without saying which schema they index into.

Make the request shape unambiguous:

- Add ParquetPushdownRequest.SchemaId (Iceberg schema id) to the
  proto and to the design's API sketch.
- Document the binding contract in the design: the predicate must
  carry only field-id references; the connector binds before
  sending, the server checks ids against the schema.
- Validation now rejects (predicate set, schema_id == 0) with
  InvalidArgument before any work is done. Deeper "every field id
  exists in the snapshot's schema" check needs catalog access and
  lands in M3.
- Update / add tests covering the new gate.

2026-04-25 15:07:12 -07:00

..

daemon

parquet_pushdown(M0): cover daemon Config validation, especially connector-trusted gating

2026-04-25 13:44:36 -07:00

request_validation_predicate_test.go

parquet_pushdown: predicate must be a bound expression with schema id

2026-04-25 15:07:12 -07:00

request_validation_test.go

parquet_pushdown: predicate must be a bound expression with schema id

2026-04-25 15:07:12 -07:00

request_validation.go

parquet_pushdown: predicate must be a bound expression with schema id

2026-04-25 15:07:12 -07:00

service_grpc_test.go

parquet_pushdown(M0-C6): add bufconn integration test

2026-04-25 13:44:10 -07:00

service.go

parquet_pushdown(M0-C2): add service skeleton and request validation

2026-04-25 13:39:28 -07:00

stats.go

parquet_pushdown(M0-C2): add service skeleton and request validation

2026-04-25 13:39:28 -07:00