SQL with filter condition "or" can not be pushed down to Iceberg metadata when do sql plan

[Xiangakun]

SQL with filter condition "or" (e.g. ' select * from iceberg.iceberg_schema.tableA where id = 1 or data = 'test' ') can not be pushed down to Iceberg metadata when doing sql plan stage, which lead to such scenario can not make full use of iceberg’s MIN/MAX index. As far as I know, Iceberg itself supports filter with 'or' condition. I am wondering if it's the limit by current framework of trino ？Does anyone has good idea on this？ Thanks in advance

[Xiangakun]

I am now using trino with version: 355

[findepi]

This is going to be covered by #7994.
See #18 for more info.