If your only concern is about memory utilization, I would try estimating this using the plan's cost. But I guess you'll have run some tests to estimate the ranges you can accept.
On Sun, Feb 16, 2020 at 5:50 PM Yang Liu <[email protected]> wrote: > 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 >
