This is a work in progress that aims to support more filters.
My first goal is to support the IN but I'll likely need to support more I'm not sure exactly what the ExpressionClass I'm supporting exactly contains.
@Mytherin, few questions to move forward:
Is adding a vector<unique_ptr<Expression>> in MySQLBindData instead of input.filters from TableFunctionInitInput &input the right approach? Won't I run in a side effect or anything else?
Should I figure out how to move from a vector<unique_ptr<Expression>> to a vector<unique_ptr<TableFilter>> &filters or should I update all the filter pushdown logic to support vector<unique_ptr<Expression>> instead?
This is a work in progress that aims to support more filters. My first goal is to support the
INbut I'll likely need to support more I'm not sure exactly what theExpressionClassI'm supporting exactly contains.@Mytherin, few questions to move forward:
vector<unique_ptr<Expression>>inMySQLBindDatainstead ofinput.filtersfromTableFunctionInitInput &inputthe right approach? Won't I run in a side effect or anything else?vector<unique_ptr<Expression>>to avector<unique_ptr<TableFilter>> &filtersor should I update all the filter pushdown logic to supportvector<unique_ptr<Expression>>instead?Thanks!