Generally speaking, the SEARCH operator is very good, but when we use Calcite to optimize the logical plan and then use Spark to execute, this is unsupported. So is there a more elegant way to close the SEARCH operator? Or how to convert the SEARCH operator to the IN operator before converting the Calcite logical plan to the Spark logical plan? If we do this, we need to consider Join / Filter, are there any other RelNodes?
Maybe, this optimization is optional more better at present for many query execution engine does not support this operator?
