Hello, I'm coming across this exception when Calcite prepares queries in parallel. I see this happens if the same query is getting planned by two threads at the same time, but I also have the impression that this may also happen when the two queries being planned in parallel are not exactly the same but have common fragments of the logical plan.
Since this is hard to reproduce and debug as it happens rarely in a multithreaded setup, I'd like to have some workaround of the problem. What would be a good practice? For example, if the exception is caught and then the planning re-attempted (a few times if needed), would that significantly decrease the probability of running into that exception? Thanks in advance for any help! -- Boyan Kolev
