You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BadQueryRequestException is currently used when a bad query is passed by client. When we classify BadQueryRequestException for QueryException, it's reported as QueryException.QUERY_EXECUTION_ERROR (200). The issue is QueryException.QUERY_EXECUTION_ERROR code is too generic which doesn't really tell much about the nature of this failure.
Issue Description
BadQueryRequestException
is currently used when a bad query is passed by client. When we classifyBadQueryRequestException
forQueryException
, it's reported asQueryException.QUERY_EXECUTION_ERROR
(200). The issue isQueryException.QUERY_EXECUTION_ERROR
code is too generic which doesn't really tell much about the nature of this failure.BadQueryRequestException Usage
List of BadQueryRequestException uses. They are all client side bad queries such as
Examples
Assuming company_id is a numeric type, this will error with something like
How to reproduce
Pick an integration test like OfflineClusterIntegrationTest, and try a new test case function
Suggested Fix
In org/apache/pinot/core/query/executor/ServerQueryExecutorV1Impl.java, we can classify this as
QueryException.QUERY_VALIDATION_ERROR
instead of genericQueryException.QUERY_EXECUTION_ERROR
to indicate this is a client side error.The text was updated successfully, but these errors were encountered: