I must comment that I am disappointed with this resolution. It is kind of ridiculous for the Hibernate team to be judging that it is "bad application design to be doing such large IN element restrictions". Our application functions extremely well, is very performant, and we have customers all over the world that are paying for it. We have the infrastructure to handle this kind of querying, and that data sets that require it. What we do not have is a Hibernate that supports our use case with IN, or the temporary table / common table expression support as better alternative (so we are left with IN).