Wrong error message for incorrect column name during lookup

Hi team, we believe that the error message could be more informative when sendin a query using the lookup on a dimension table.

If we have an incorrect column name on the metric table in the look up query, it gives us an invalid segment/s error and returns no result. If we have an incorrect column name on the dimension table in the look up query, it gives us a QueryExecutionError.

I think that if there is an incorrect column name on the metric table, it should give a QueryExecutionError instead of invalid segment/s error.

Start by reproducing the lookup query with an incorrect column name on the metric table and compare its response with the dimension-table case. Trace the lookup query handling and error classification to determine where the invalid segment error is produced; done means the metric-table case returns QueryExecutionError instead of no results.

Written by the indexing model from the issue text.