Is it possible to have some limitations on the SQLs to make sure our application which depends on Calcite is "safe"? For example, when do merge joining between 2 large datasources, our application maybe OOM since the joining process is in memory. If we have the "limitation mechanism", we can refuse to execute the joining to avoid OOM.
Or we can only do the check outside Calcite? Thanks
