Apache Druid

not that i am aware of through configuration. you could get it through a code change of course.

another way of approaching the problem is to set `-XX:HeapDumpOnOutOfMemoryError` and look at what's in the heap when the OOME is there. It will include the Query object corresponding to the query that tripped you up. It will also include the actual objects that tripped you up, which would be useful as well

if you figure out what it is, please let us know so we can ensure it does not occur in the default configuration (when using `bin/start-druid`)

Right, I dig the code a little bit, it seems that in class `SqlLifecycle` we can add the logging in `initialized()` . Otherwise, the logging from `emitLogsAndMetrics` would only be afterward. Similar story applies to native query side in broker rest end point too.

Do you feel this is a feature we can potentially add to the current code?

It could be a useful option, or even, we could _always_ log to the Broker log file at "debug" level. That way, people can see it if they want to by enabling debug logging