You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2019/03/11 11:16:09 UTC

[GitHub] [incubator-iceberg] prodeezy commented on issue #123: Add support for struct field based filtering

prodeezy commented on issue #123: Add support for struct field based filtering
URL: https://github.com/apache/incubator-iceberg/pull/123#issuecomment-471499273
 
 
   > General API design related question - how do we bubble up in the API layer the fact that we are supporting the struct field based filtering but not other nested field types filtering? ..  I am just curious what a client's expectations should be that the API exposes this new capacity in a coherent manner.
   
   @fbocse  Currently it would be implied. The only feedback the client gets right now is in the Physical plan, that this filter is pushed down to Iceberg Scan level and if the client inspects the Scan (using  iceTable.newScan().filter(structFilterExp).planFiles ) , should be able to notice the appropriate files being skipped. AFAIK, this is consistent with how top-level field based filter expressions currently communicate to the client.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org