szehon-ho commented on issue #5132:
URL: https://github.com/apache/iceberg/issues/5132#issuecomment-1167949178
Actually I had a thought of an optimization, I think for struct column
predicate we can pushdown to the nested columns like:
where col= struct{10, 'data'} => col.a = 10 and col.b='data'
It does get a bit trickier with collections (can be IN?)
So the open-ended question is 1) whether we should do it 2) whether Iceberg
should do it or Spark should do it generically. Open to thoughts on this, and
doing it as a second phase.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
