You will get the following error: The future returned an exception of type: ing.wbaa.druid.client.HttpStatusException, with message: Received response with HTTP status code 500 Internal Server Error.
For more detailed view, in the broker logs you will get the corresponding error:
2021-05-24T06:54:21,145 WARN [qtp856880372-124[timeseries_[wikipedia]_72afa724-fcac-498f-b5ef-31fe5da69175]] org.apache.druid.server.QueryLifecycle - Exception while processing queryId [72afa724-fcac-498f-b5ef-31fe5da69175] (java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer)
2021-05-24T06:54:21,149 ERROR [qtp856880372-124[timeseries_[wikipedia]_72afa724-fcac-498f-b5ef-31fe5da69175]] org.apache.druid.server.QueryResource - Exception handling request: {class=org.apache.druid.server.QueryResource, exceptionType=class java.lang.ClassCastException, exceptionMessage=java.lang.String cannot be cast to java.lang.Integer, query={"queryType":"timeseries","dataSource":{"type":"table","name":"wikipedia"},"intervals":{"type":"LegacySegmentSpec","intervals":["2011-06-01T00:00:00.000Z/2017-06-01T00:00:00.000Z"]},"descending":false,"virtualColumns":[],"filter":null,"granularity":"HOUR","aggregations":[{"type":"count","name":"count"}],"postAggregations":[],"limit":2147483647,"context":{"lane":"low","priority":"-1","queryId":"72afa724-fcac-498f-b5ef-31fe5da69175"}}, peer=172.21.0.1} (java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer)
The error can be fixed by representing the priority value by an integer, for example:
When setting, for example, a priority parameter value in the query context as a string value (e.g., "1") like below:
and in Druid we have query laning enabled, for example with the following settings:
The resulting query (with some additional defaults (lane, and query id)) is the following:
You will get the following error:
The future returned an exception of type: ing.wbaa.druid.client.HttpStatusException, with message: Received response with HTTP status code 500 Internal Server Error.
For more detailed view, in the broker logs you will get the corresponding error:
The error can be fixed by representing the priority value by an integer, for example: