Pinot returns empty result set when there is an invalid column

Would it make sense to add a config flag to fail a query if a column which does not exist is in a select statement?
ex. `select from table` produces an empty result set but no error.

No file, test, or entry point is named. Start by reproducing the query with an invalid selected column in Pinot, then trace where query validation and configuration are handled. Done means a configurable failure for missing selected columns, with tests covering the flag and the existing behavior.

Written by the indexing model from the issue text.