pmmag commented on issue #17821:
URL: https://github.com/apache/druid/issues/17821#issuecomment-2782546922
I tried your example in a fresh docker compose with both 31.0.0 and 32.0.1
(with the sample compose file and environment file linked in the docs).
For me when I run the groupBy query right after the data has been inserted,
I actually do get
```
{
"error": "Unknown exception",
"errorClass": "java.lang.RuntimeException",
"host": "172.21.0.5:8083",
"errorCode": "legacyQueryException",
"persona": "OPERATOR",
"category": "RUNTIME_FAILURE",
"errorMessage": "java.util.concurrent.ExecutionException:
java.lang.ClassCastException: class [J cannot be cast to class
[Ljava.lang.Object; ([J and [Ljava.lang.Object; are in module java.base of
loader 'bootstrap')",
"context": {
"host": "172.21.0.5:8083",
"errorClass": "java.lang.RuntimeException",
"legacyErrorCode": "Unknown exception"
}
}
```
However, if I run the groupBy even once with `vectorize: false`, then
afterwards all subsequent queries with `vectorize: true` will work (which is
not the case with our actual Druid 31.0.0 installation, where we get the error
every time)... Perhaps this is some kind of user error or I just need to wait
longer after inserting the data?
I also tried to change the help and error codes to contain non-numeric
characters (as they do in our case), as well as tweak the timestamps and
partitioning (e.g., "by month") to see if it matters when the data is not in
the same time range. But it made no difference, I still always only get the
error until I make one query with `vectorize: false`. Yet, in our real world
datasources, the errors persist.
So yes, it seems to be difficult to reproduce, and I guess there must be
some other factor at play in our real world setup where it happens every time
(?). The original datasources in question are using Kafka-based ingestion, in
case that matters.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
