[GitHub] [pinot] Jackie-Jiang commented on issue #10753: Wrong error message for incorrect column name during lookup

["Jackie-Jiang (via GitHub)" <gi...@apache.org>]

Jackie-Jiang commented on issue #10753:
URL: https://github.com/apache/pinot/issues/10753#issuecomment-1572801823

   This warning is appended because these segments do not contain the column asked, thus being pruned before query execution. `QueryExecutionError` is reported when an error occurred during query execution.
   Ideally we should also report invalid segments when the column name is incorrect on a dimension table, but since dimension table is maintained differently (we maintain the whole table on heap), segment pruning step is not happening for dimension table.
   I can see the error message is slightly confusing because a common case when query contains a column that doesn't exist in the segment is when user just added a column into the schema but forgot to reload the table.
   
   Are you running the latest Pinot version? I think the latest version should throw exception on the broker side if a column doesn't exist in the table schema


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org