IF I create a view that is a union of partitioned parquet files and a database that has secondary indexes, will Drill be able to properly push down query limits into both parts of the union?
In particular, if I have lots of archival data and parquet partitioned by time but my query only asks for recent data that is in the database, will the query avoid the parquet files entirely (as you would wish)? Conversely, if the data I am asking for is entirely in the archive, will the query make use of the partitioning on my parquet files correctly?
